RE: [us...@httpd] ProxyPass and Internal URLs

2009-05-07 Thread Gund Wehsling
Hi Thanks for the quick response. 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. Yes, internaladdress1.com is not routable or resolvable unless you are on the LAN

Re: [us...@httpd] ProxyPass and Internal URLs

2009-05-07 Thread John Oliver
On Thu, May 07, 2009 at 12:02:40PM -0400, Eric Covener wrote: > On Wed, May 6, 2009 at 11:31 PM, Gund Wehsling 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 fi

Re: [us...@httpd] ProxyPass and Internal URLs

2009-05-07 Thread Eric Covener
On Wed, May 6, 2009 at 11:31 PM, Gund Wehsling 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 wit