On Thu, May 07, 2009 at 12:02:40PM -0400, Eric Covener wrote: > On Wed, May 6, 2009 at 11:31 PM, Gund Wehsling <gund@xxxxxxxxxxx> wrote: > > 4. But, for some reason, if I open https://publicaddress1.com, I get 404 and > > the browser address bar shows http://internaladdress1.com and all the > > relevant link work fine, the site functions well and as exzpected. I tried > > to rewrite with as much mixed success as there are opinions to do this... > > It sounds like your ProxyPassReverse failed to do the right thing, and > a redirect leaked out. I assume for most users, "internaladdress1.com" > in the browser would be game over. I just set up something like this, where a Red Hat Linux host has a public IP and redirects certain URLs to Tomcat on a Windows machine via a private network. A single ProxyPass line worked for me... the "Proxy" implies that the Apache httpd on the host with the public address is actually proxying, not redirecting, and so the private IP should never be visible to the client. Try commenting out the ProxyPassReverse I don't think you need it. -- *********************************************************************** * John Oliver http://www.john-oliver.net/ * * * *********************************************************************** --------------------------------------------------------------------- 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
|