Using PATH_INFO as your full docroot (was Re: Sending data to browser's URI field via POST)

(Before you suggest it merlyn, PATH_INFO is not an option in this case).

Really? Why? Can you explain? I just added this to my httpd.conf (updated slightly for simplicity):

Listen 127.0.0.1:8801
<VirtualHost 127.0.0.1:8801>

  Alias /images/ /Users/merlyn/Sites/virtualroots/images/
  Alias /icons/ /usr/share/httpd/icons/
  ScriptAlias / /Users/merlyn/Sites/virtualroots/virtualroot/

</VirtualHost>
[download]

And then I created /Users/merlyn/Sites/virtualroots/virtualroot as a shell executable script:

#!/bin/sh
echo content-type: text/plain
echo

printenv
[download]

And now I can visit http://localhost:8801/some/place?key=value, and my CGI script is called with /some/place as the PATH_INFO and key=value for the QUERY_STRING. And I can visit /images/ and get a directory listing with the right icons, and files there are also served properly.

So, explain again why you're allergic to PATH_INFO?

-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.

Comment on Using PATH_INFO as your full docroot (was Re: Sending data to browser's URI field via POST) Select or Download Code