[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [users@httpd] mod_proxy_http rewrite problem

Or if you want to masquerade /frontpage completetly, you could use
>   mod_proxy_html to rewrite response URLs on the fly.

Anybody have suggestions on how to masquerade /frontpage to rewrite responses?

On Fri, Jun 15, 2018 at 12:33 PM, Herb Burnswell <herbert.burnswell@xxxxxxxxx> wrote:
What if you remove the ProxyPassReverse, leaving the 2 ProxyPass only? 

Thanks Yann.

Unfortunately no, without the ProxyPassReverse directive the behavior is the same, it just loops.  The 302's are in the access log over and over: - - [15/Jun/2018:12:16:40 -0700] "GET /frontpage/login.zul HTTP/1.1" 302 - "-" "Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0" "305C0B70515B838AE70AC0F7DBA79799.node3"

On Thu, Jun 14, 2018 at 11:34 PM, Yann Ylavic <ylavic.dev@xxxxxxxxx> wrote:
On Fri, Jun 15, 2018 at 12:34 AM, Herb Burnswell
<herbert.burnswell@xxxxxxxxx> wrote:
>> If you accept that /frontpage path going up to the client/browser once
>> the first / works, then you can:
>>    ProxyPass / balancer://applicationcluster/frontpage/ ...
>>    ProxyPass /frontpage/ balancer://applicationcluster/frontpage/ ...
>>    ProxyPassReverse / balancer://applicationcluster/frontpage/
>> The two ProxyPass handle the two kind of paths to forward (the
>> longuest match should be elected first).
> Using the two ProxyPass directives per above sends a request into a loop.

What if you remove the ProxyPassReverse, leaving the 2 ProxyPass only?


To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx