Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

404 error at https://nodejs.org/dist/latest-v6.x/docs/api #1391

Closed
mrspaghetti opened this issue Oct 6, 2017 · 10 comments
Closed

404 error at https://nodejs.org/dist/latest-v6.x/docs/api #1391

mrspaghetti opened this issue Oct 6, 2017 · 10 comments

Comments

@mrspaghetti
Copy link

  • URL:
  • Browser version:
  • Operating system:
@knksmith57
Copy link

looks like this isn't isolated to LTS docs, but all linked API doc revisions:

❯ curl -iI https://nodejs.org/docs/latest-v4.x/api/
HTTP/1.1 404 Not Found
Date: Fri, 06 Oct 2017 17:26:55 GMT
Content-Type: text/html
Connection: keep-alive
Set-Cookie: __cfduid=d2d6164c76c80f031477a5d16976158131507310815; expires=Sat, 06-Oct-18 17:26:55 GMT; path=/; domain=.nodejs.org; HttpOnly
CF-Cache-Status: HIT
Server: cloudflare-nginx
CF-RAY: 3a9a5416d9df58f1-DFW

affecting:

can we get someone from core to look at this pretty please?

@jasnell or @mikeal maybe?

@knksmith57
Copy link

money says this is related to #1387.

@fhemberger is it possible this is simply a caching issue w/ cloudflare?

@fhemberger
Copy link
Contributor

Seems to be a Cloudflare issue. Works fine for me (tested from Germany and via VPN from the US).

@knksmith57
Copy link

Links are still busted for me.

For the rest of the world, static mirrors:

happy to add more versions at request if the issue persists.

@fhemberger
Copy link
Contributor

Hello @nodejs/build, can you please look into this?

@joaocgreis
Copy link
Member

Links also work for me.

I've cleared the Cloudflare cache, don't know if that will help.

This is a duplicate of #1390 and nodejs/build#905 .

@fhemberger
Copy link
Contributor

Closing this one in favor of nodejs/build#905. Please comment there If the issue still persists on your side.

@refack
Copy link
Contributor

refack commented Oct 7, 2017

@fhemberger trying to figure out what CF is caching... Was there a time window where the /docs/* paths didn't work?

@evanlucas
Copy link
Contributor

/cc @rvagg? I think this has happened once before?

@gibfahn
Copy link
Member

gibfahn commented Oct 7, 2017

Can we comment on nodejs/build#905 instead? Otherwise we just get duplicates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants