Your use of ProxyPassReverse is wrong...
http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxypassreverse
On Nov 26, 2012, at 3:27 PM, Dave Shevett <shev...@pobox.com> wrote:
> On 11/26/12 3:12 PM, Jim Jagielski wrote:
> # Working, live production host:
> ProxyPass
> /a/
> ajp://10.211.42.48:8009/
> ProxyPassReverse
> /a/ http://FOO.com/
>
>
> # app test host
> ProxyPass
> /c/
> ajp://10.122.95.146:8009/
> ProxyPassReverse
> /c/ http://FOO.com/
>
>> The first Proxy configuration is working correctly. Requests coming into
>> /a/ go to the server on 10.211.42.48. No worries. But hitting the second
>> address will end me back up at /a/ - I'm guessing because there are
>> essentially two ProxyPassReverse's for the same url (http://FOO.com
>> ).
>>
>>
>> Do you mean that
>>
>>
>> http://FOO.com/a/
>> goes to ajp://10.211.42.48:8009/
>>
>> But
>>
>>
>> http://FOO.com/c/
>> DOES NOT go to ajp://10.122.95.146:8009/
>>
>> but instead goes to ajp://10.211.42.48:8009/ ??
>>
>
> Not exactly. The request to http://FOO.com/c/ initially goes to
> ajp://10.122.95.146:8009/
>
> That host gives a redirect ('not logged in'), and redirects to
> HomePage.action. But the redirect as received by the browser is /a/, not
> /c/, I assume due to the proxypassreverse earlier in the vhost definition.
>
>
> --
> Dave Shevett
>
> shev...@pobox.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org
