Thanks for the response, Joshua. Unfortunately, that didn't do the trick. When I appended the :80 to the ServerName directive, I simply got "Cannot find server" messages when attempting to access http://myserver/dir (no trailing slash). I may have to move to using a separate Apache server to handle these requests, however I'm a bit concerned due to the number of virtual hosts operating on this server. Chris On Tue, March 4, 2008 4:02 pm, Joshua Slive wrote: > On Tue, Mar 4, 2008 at 3:53 PM, Christopher Bianchi <chris@xxxxxxxxxx> > wrote: > >> The problem is that I have Apache (2.0.63) running behind a firewall on >> port 8080. Squid (2.6b18) is the proxy running on port 80. >> >> When Apache receives a directory request without a trailing slash, its >> redirect includes its running port (e.g. http://myserver/dir is >> redirected >> to http://myserver:8080/dir/). 8080 is user inaccessible and the >> redirect >> fails. >> >> How do I prevent Apache from affixing the port into the URL redirect? >> Does >> Apache need to know that it's running behind a reverse proxy? > > Normally the proxy is responsible for fixing this up (as the apache > proxy will do with the ProxyPassReverse directive). I'd guess squid > could do it with the right config. > > But you can get apache to lie about its own name and port using something > like > ServerName myserver:80 > UseCanonicalName On > > Joshua. > --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|