httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Plüm, Rüdiger, Vodafone Group <>
Subject RE: [PATCH] Balancers, VirtualHost and ProxyPass
Date Wed, 10 Dec 2014 12:49:36 GMT
But this way we lose the base ones that are not touched in the virtual host and e.g. are only
used by rewriterules.
So we should transfer the base ones to the merged array in any case and update them where
Isn't the config merge on a critical path with every request? So double for loops always worry
me a little bit from performance point of view.



> -----Original Message-----
> From: Jan Kaluža []
> Sent: Mittwoch, 10. Dezember 2014 13:26
> To: httpd
> Subject: [PATCH] Balancers, VirtualHost and ProxyPass
> Hi,
> I've found out that following configuration does not work as expected:
> <Proxy balancer://a>
>     ...
> </Proxy>
> <VirtualHost *:80>
>      ProxyPass / balancer://a stickysession=JSESSIONID|jsessionid
> </VirtualHost>
> In this case, two proxy_balancers are created. The first one in Proxy
> section in the main config without stickysession and the second one in
> the vhost section with stickysession set.
> Because of merge_proxy_config behaviour, the one from the main config is
> always preferred and therefore you cannot set stickysession (and other
> options) this way.
> Attached patch fixes that by changing the merge strategy for balancers
> array to merge options set by ProxyPass.
> I think we would need the same for proxy_worker too, but before I spent
> afternoon working on it, I wanted to ask, do you think this is the right
> way how to fix this?
> Regards,
> Jan Kaluza
View raw message