Re: Reverse Proxy

["Mike Eovino" <meovino@xxxxxxxxx>]

I got it working.  Rather than specifying a page, Apache is happier
when you specify a directory.

ProxyPass /enet/ http://199.5.86.71/
ProxyPassReverse /enet/ http://199.5.86.71/

Now for my next question.  Is there any real reason to use the WAS
plugin instead of a reverse proxy to run the HTTP server on one system
and WAS on another?  Ideally, that's what we're aiming for, the
ability to run the HTTP server(s) in the DMZ and WAS in the secure
area of the network.

Thanks!

Mike E.

On 4/5/06, Mike Eovino <meovino@xxxxxxxxx> wrote:
> I am experimenting with allowing public access to an HTTP server
> that's on a publicly
> inaccessible box.  It seems simple enough, but I can't seem to get it
> to work properly.  It looks as if the server is just rewriting the URL
> to the internal address, rather sending the request to the back end
> server, getting the response and sending it on through.
>
> Here's what the admin GUI added to my config file:
> ProxyPass /login.jsp http://199.5.86.71/login.jsp
> ProxyPassReverse /login.jsp http://199.5.86.71/login.jsp
>
> When I attempt to access http://www.simplyexpresslink.com/login.jsp,
> the URL gets rewritten in the address bar to
> http://199.5.86.71/login.jsp
>
> I'm sure I'm missing something, but everything I see on the web tells
> me that this should work.
>
> Thanks!
> Mike E.
>