Re: mod_perl

[John Edstrom <edstrom@Poopsie.hmsc.orst.edu>]

Jay Austad
> 
...
> 
> The results are below, first the frames, then noframes, and finally
> just /cgi-bin/store.  The frames and noframes options are acceptable,
> but the last one is where it's really loading the server down.  Isn't
> /cgi-bin/store the same thing as /cgi-bin/store/noframes?  

No, not necessarily.  frames/noframes direct minived to the pages
frames.html and noframes.html.  Just /cgi-bin/store just brings up the
cgi program without a target.  

> They return
> the same thing.  So what extra stuff is happening when I don't give
> the frames or noframes option?

Normally Apache will try (in the rewrite stage, I think) to find what
this "wild card" URI should map to.  Options are in the DirectoryIndex
definition in httpd.conf; it looks for index.html, index.htm,
index.... whatever you have in your config.  Apache tries to find an
acceptable file by issuing subrequests for each of the options. This
behavior is silent if all Apache is doing is looking for a file in a
directory tree.  But if the URI is connected to an action, that action
will be attempted for possible target.  You see this if you try to
access a protected directory as http://host/path/, you will get an
auth challeng for each DirectoryIndex listed.

Depending on how you have your server configured, you may be spraying
yourself with subrequests for /cgi-bin/shop/index.html,
/cgi-bin/shop/index.htm, etc.  Instead of finding or not finding the
optional directory indexes, Apache may be invoking invoking the cgi
program with various suffixes and each one will spawn a minivend
child.  That is my guess anyway.

try 
	http://localhost/cgi-bin/shop/index.html


> 
> Jay
> -

-- 
 John Edstrom | edstrom @ slugo.hmsc.orst.edu