Re:Cloudflare Pages: Best server tech since CGI-bin?
by qbasic_forever on Sunday October 23, 2022 @05:18PM
(#33310343)
It was removed explicitly for SEO and having a single canonical URL for a resource _for all of time forever_. Right now we use HTML for web pages but who knows what the internet 20, 50, 100, etc. years from now will use--maybe .Super-Awesome-Mega-HTML is all the rage. If over time you are changing your site and its URLs are changing then you're breaking that canonical URL and search indexes, caches, way back machine, etc. all suffer. So the intent is don't make the format of the page (HTML) part of it's canonical URL.
[ Parent
| on HN ]
Re:Cloudflare Pages: Best server tech since CGI-bin?
by hombre_fatal on Sunday October 23, 2022 @07:01PM
(#33311149)
The benefits aren’t just SEO. I’d much rather have /about than /about.{htm,html,php,asp,etc}. I don’t see how the latter is preferable for routing to pages.
Re:Cloudflare Pages: Best server tech since CGI-bin?
by cube00 on Sunday October 23, 2022 @07:02PM
(#33311158)
In case anyone hasn't read it, not including the extension is covered in more detail in "Cool URIs don't change" https://www.w3.org/Provider/Style/URI
Re:Cloudflare Pages: Best server tech since CGI-bin?
by paraknight on Monday October 24, 2022 @02:05AM
(#33313398)
I second this. That's what mime-type headers are for. The URL should locate a resource, as the name suggests, not necessarily convey metadata about what the resource is.