Okay, here's this thing that really goes on my tits, internet-wise. Namely, all those crufty URIs hanging around all over the web with their ghastly .cgi and .pl. That's bad, because it isn't forward compatible. Perl guys like us are responsible.
Imagine you have programmed a super excellent piece of web software, say a dictionary application, and installed it in http://example.com/dict.pl. What if one day Perl isn't good enough because it's much more excellent in Rules on Raiby or HPH or whatever - then you deploy the new one with a different URI and bookmarks and links break and your loyal users are up in arms.
By content negotiation, a feature built into HTTP, you can have your link be http://example.com/dict. You are able to switch the implementation, but the interface stays the same. Properly configured, the web server will know what to run.
So, in conclusion, it's not necessary to expose the underlying technology through the URI. The next time you administrator types are going to deploy a new Apache2, use the config below and you web author types make sure to link to resources without the file endings.
http://httpd.apache.org/docs/2.2/ http://perl.apache.org/docs/2.0/user/config/config.html<IfModule mime_module> AddHandler cgi-script .cgi # .cgi files are handled by mod_cgi </IfModule> <IfModule negotiation_module> MultiviewsMatch Any </IfModule> <IfModule perl_module> <Files *.pl> # .pl files are handled by mod_perl2 SetHandler modperl PerlResponseHandler ModPerl::Registry </Files> </IfModule>
In reply to URI Style by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |