www subdomain not working

www subdomain not working

Please amend When using Firefox at computers other than my own, I will type in "translatewiki + Shift + Enter" which the browser then redirects to http://www.translatewiki.net/ but that URI can't be found. Although the days of a "www" subdomain are long ago, it's still worth maintaining these to redirect to the proper https://translatewiki.net/

Koavf (d) (en-N/en-US, es-2/es-US, de-1, pt-1)20:56, 16 October 2016

What version of Firefox is this? I've never seen such a behaviour.

Nemo (talk)06:43, 17 October 2016

Every version since at least 2.x has had this. Have you tried it?

Koavf (d) (en-N/en-US, es-2/es-US, de-1, pt-1)06:51, 17 October 2016

Ah, I see now. I had missed the shift.

Nemo (talk)19:52, 19 October 2016

Is this the best place to post bugs? I don't see a Village Pump here, so I figure this is the most centralized discussion space.

Koavf (d) (en-N/en-US, es-2/es-US, de-1, pt-1)21:52, 19 October 2016
 
 
 

DNS/Apache config needed? Who has the ops access to twn server?

Liuxinyu970226 (talk)03:09, 29 November 2016

I am not convinced this is worth the hurdles of adding DNS records and redirects and making sure HTTPS is not broken.

Nike (talk)10:06, 21 May 2017

If you think that adding an HTTP redirect is too difficult then that is definitely a problem. I'm 100% certain that there are incoming links which include a www subdomain so if you want incoming viewers to think the site is still functional, I would recommend adding it.

Koavf (d) (en-N/en-US, es-2/es-US, de-1, pt-1)17:47, 21 May 2017

Redirects are hard nowadays, yes. See for instance phabricator:T133548. Closed.

Nemo (talk)22:31, 22 May 2017

Well, several dozen of them certainly are. Much harder than one to be sure. I don't see how no response--not even a 404 page--is preferable but that's where that incoming traffic will go: nowhere http://isup.me/www.translatewiki.net

Koavf (d) (en-N/en-US, es-2/es-US, de-1, pt-1)00:49, 23 May 2017