I can't believe this is a problem with pound, and I'm still investigating...
but was wondering if this might ring a bell with anyone. It SEEMS to be a
pound problem.
By default apache provides the printenv and testcgi scripts in the global
cgi-bin directory. We have a webserver that has several IP-based virtual
hosts on it, as well as the main host IP (which just gives the apache
default install page and documentation). Any webbrowser that goes to a URL
on the virtual host goes through pound, but any web browser that goes to the
main host on that same machine does not go through pound.
Example: going to the main host and calling the cgi-bin script printenv such
as:
http://billy.somedomain.com/cgi-bin/printenv
will return the correct results
(a display of the environment)
but
http://george.somedomain.com/cgi-bin/printenv
returns a page not found
ScriptAlias is defined on the server globally, not in Virtual host
containers, so it should apply to both sites above.
I've beat my head against this for a while, and the only difference I can
come up with is the 2nd reference above goes through pound while the first
reference does not (but both go to the same server).
I'm pretty sure apache is configured correctly, and am left with the only
difference I can see is one going though pound. Has anyone seen this before
and is it something I'm missing with my pound configuration?
Thanks!
Jay West
---
[This E-mail scanned for viruses by Declude Virus]
|