[yoursunny]

I opened my website in 2006. Since 2009, I've kept all the links unchanged or redirected through two rebuilds.

It's a lot of work because I need to customize URI structure in blog systems and put complex rewrite rules.

To ensure the setup is more or less correct, I have a bash script that tests the redirects via curl. https://bitbucket.org/yoursunny/yoursunny-website/src/912f25...

[slver]

I've a bunch of small sites whose links end in ".php" despite they no longer run on PHP.

[JadeNB]

> I've a bunch of small sites whose links end in ".php" despite they no longer run on PHP.

Kudos for maintaining that compatibility, but it seems that this kind of thing is addressed in the linked document:

> File name extension. This is a very common one. "cgi", even ".html" is something which will change. You may not be using HTML for that page in 20 years time, but you might want today's links to it to still be valid. The canonical way of making links to the W3C site doesn't use the extension.

[slver]

Back then we didn’t have routers

[smhenderson]

I'm not sure if they still use it but a site I redid for a company many moons ago in Perl had Apache set to treat .htm files as CGI scripts so we didn't have to change the previous, static site's URL's.

The original site ran on IIS and was old enough that MS software at the time still used three letter extensions for backwards compatibility, around 1997-1998 IIRC.