-
Notifications
You must be signed in to change notification settings - Fork 130
redirect to nodejs.org #432
Comments
Would it better to show this message before redirecting?
|
+1 |
@WaleedAshraf That would work, but my (mild) preference would be not do that. That message has been on the iojs.org website for over 2 years. I could be wrong, but at this point, I don't think anyone will be especially helped by that message compared to simply having to infer meaning from the experience of "I went to iojs.org and got redirected to nodejs.org." Given how little attention this repo has gotten (it's build step |
@refack Any chance we can do this via a DNS change and some hopefully-trivial Cloudflare configuration? |
Shouldn’t it just be a 301 redirect? |
+1, cc @rvagg for Cloudflare bits |
@Trott Sound fine to me. 👍 |
Interestingly, if I browse to the current IP address of www.iojs.org (138.197.224.240), it already redirects to www.nodejs.org. So this is already partially setup somewhere. |
Should be.
AFAIK they are served from the same server who's default "virtual server" is the nodejs.org site, so a direct IP URL will get redirected. |
+1 to redirect. @rvagg any objections? If not unless you can think of a reason we should do something else updating the cloudlfare config as suggested sounds the easiest. If we are agreed I can probably take a look at that. |
Redirect got activated today. /download, /dist, /docs and /api remain intact but everything else goes to https://nodejs.org/ I'm going to archive this repo now. I don't see objections. End of an era, it was fun. |
It's probably about time to redirect https://iojs.org to https://nodejs.org and then archive this repository. Any objections?
/ping @nodejs/build @nodejs/website @nodejs/tsc @nodejs/community-committee
The text was updated successfully, but these errors were encountered: