On Fri, 2025-03-21 at 17:06 +1030, Tim via users wrote: > I'm not sure that's a wise idea. Now the server would have to parse > every .html file looking for PHP, rather than just the .php files. Supplemental info that may be related to why the original poster is thinking of doing this... Many years I turned on content-negotiation on my server. And instead of my links being explicit href="contact-details.html" they are simply href="contact-details" and the actual page could be a .html file today, and .asp file tomorrow, or rewritten as a .php file the next week. I don't have to change any of the links on any pages, they work for whatever contact-details.something file that I store on the server, the server automatically picks it out. As my needs for that page change, I can simply swap it out for a different kind of file. Also, it handled things like href="printer-maintenance" being a link to one page this week, but next week it's a link to a folder, with a page in that folder linking to many other adjacent pages that expand on topics. A whole page to opening the printer to remove paper jams, a whole page just for how to refill the toner, etc. It works brilliantly on Apache. It's a shame that my current hosting provider decided to ditch Apache (free software) for LightSpeed (commerical software), and it's not the drop-in replacement for Apache that LightSpeed claims it is. And my hosting provider buggers up the configuration in various ways, too. Content negotion is not just for links written in the pages, but anything someone wants to access. e.g. http://example.com/explanation is a nice neat link written in the modern style that will load the page that otherwise you would have accessed by http://example.com/explanation.shtml -- uname -rsvp Linux 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
