We are doing something more like this on our 2.4 servers:
<Proxy balancer://cd107d9706d71153bafd4ab15f1c6b5d>
BalancerMember http://backend.example.local status=-SE
</Proxy>
<VirtualHost 10.10.10.10:80>
ServerName frontend.example.local
SSLProxyEngine On
RequestHeader set X-Forwarded-Proto http
ProxyPass /helloworld/ !
ProxyPass / balancer://cd107d9706d71153bafd4ab15f1c6b5d
ProxyPassReverse / balancer://cd107d9706d71153bafd4ab15f1c6b5d
</VirtualHost>
--
Jeremy
On Thu, September 26, 2013 4:58 am, Thomas Eckert wrote:
> Using a config like this
>
> <Proxy balancer://cd107d9706d71153bafd4ab15f1c6b5d>
> BalancerMember http://backend.example.local status=-SE
> </Proxy>
> <VirtualHost 10.10.10.10:80>
> ServerName frontend.example.local
> SSLProxyEngine On
> RequestHeader set X-Forwarded-Proto http
> <Location /helloworld/>
> ProxyPass !
> ProxyPassReverse !
> </Location>
> <Location />
> ProxyPass balancer://cd107d9706d71153bafd4ab15f1c6b5d
> ProxyPassReverse
> balancer://cd107d9706d71153bafd4ab15f1c6b5d
> </Location>
> </VirtualHost>
>
> should I not expect requests to /helloworld/ to be mapped to the files
> being served directly from frontend.example.local instead of being proxied
> away to backend.example.local ? In other words, backend.example.local
> should not even see that request.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|