Re:Contemplating the possible retirement of Apache OpenOffice
by LoSboccacc on Friday September 02, 2016 @06:25AM
(#12412059)
aaaaauuuurrrrgh that's sound in principle but placing 301 on a domain like that is really, really bad.
[ Parent
| on HN ]
Re:Contemplating the possible retirement of Apache OpenOffice
by jacquesm on Friday September 02, 2016 @06:37AM
(#12412096)
Agreed, but in this case those reasons actually make it more valid, because there will be no way for someone else to reverse the decision once it is made.
It closes the door on some zombie resurrection of openoffice and essentially cedes the identifier to libreoffice.
Re:Contemplating the possible retirement of Apache OpenOffice
by ohthehugemanate on Friday September 02, 2016 @09:04AM
(#12412700)
301 redirects are the herpes of the Internet.
You make one mistake, and it's with you for the rest of eternity.
Re:Contemplating the possible retirement of Apache OpenOffice
by greenshackle on Friday September 02, 2016 @11:56AM
(#12413892)
Oh shit, thanks, I had just set up a 301 redirect on my personal page this morning when I meant to use a 302, your post made me realize the mistake.
I was sure it was the other way around 301->temporary, 302->permanent.
Re:Contemplating the possible retirement of Apache OpenOffice
by fiatjaf on Friday September 02, 2016 @08:05AM
(#12412424)
GitHub Pages sends 301 redirects when you put a CNAME file on the repo. That's insane.
Re:Contemplating the possible retirement of Apache OpenOffice
by vog on Friday September 02, 2016 @07:09AM
(#12412186)
Indeed, it should be 307 instead, just to keep the decision revertible.