Posted by Michael Fesser on 11/11/06 00:53

..oO(Jerry Stuckle)

>Let me give you an example from one site. Most of the site is written
>in VBScript (.asp). However, we have a discussion forum written in
>Perl. We have other packages written in PHP. And we're looking at
>adding another package which requires Python.

Everything is possible, at least on Apaches.

> Of course this is on IIS, so there's no .htaccess.

There's not even a webserver ... SCNR

>But I guess if you
>dug deeply enough there might be a way to tell the server to parse
>index.html as .asp code, but blog.html as PHP code and discussion.html
>as Perl code.

Apache: Options +MultiViews

http://example.com/index.html.asp
http://example.com/blog.html.php
http://example.com/discussion.html.pl

That's it. You could even remove the '.html' from the filenames and
still call them how it's supposed to be in the most userfriendly way:

http://example.com/
http://example.com/blog
http://example.com/discussion

That's the whole point of a URL - it describes (OK, it _locates_) a
resource on a network. It doesn't have to reveal technical details about
how that resource is created or which variant of it is returned on
request. Whether it is created from a static file, a PHP script, a Perl
script or anything else - it simply dosen't matter and is of absolutely
no interest for the user agent, so it doesn't have to appear in the URL.

Micha

[Back to original message]