Why? If a balancer is used just in a Vhost, then it should be defined just in that Vhost. I can't see adding complexity and workarounds to hack around what is a simple config "error".
> On Dec 10, 2014, at 7:52 AM, Yann Ylavic <ylavic....@gmail.com> wrote: > > Hi, > > didn't look at the patch yet, but the workaround for this is usually > to use ProxySet in the <Proxy> block. > I agree that it would be nice to have these parameters merged, though. > > Regards, > Yann. > > > On Wed, Dec 10, 2014 at 1:25 PM, Jan Kaluža <jkal...@redhat.com> wrote: >> 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
