On Tue, Aug 25, 2015 at 10:48 AM, Plüm, Rüdiger, Vodafone Group <[email protected]> wrote: > I think the current state of 2.2.31 breaks existing 2.2.x configuration prior > to 2.2.31. > Prior to 2.2.31 you could do the following: > > <Proxy Balancer://proxy1> > BalancerMember ajp://127.0.0.1:7001 > BalancerMember ajp://127.0.0.2:7002 > </Proxy> > > <virtualhost *:80> > ProxyPass / balancer://proxy1/ > </virtualhost> > > <virtualhost 127.0.0.1:8080> > > <Location /bmanager> > sethandler balancer-manager > </Location> > > </virtualhost> > > With this configuration you could provide your reverse proxy to the outside > world while having the > balancermanager managing the balancer only listening to localhost. This is > not possible any longer with 2.2.31 > as the worker->s is now different in each virtualhost whereas before it was > the same as the worker->id was used > to identify the scoreboard slot.
You are right, the old behaviour was to share the score of the main server for all the vhosts that use it. I thought that since the worker's parameters are per vhost, each vhost's worker had its own score so that e.g. an error on one of them would not affect the error state of the others. I can (and indeed always unconsciously did) live with the fact that the scored parameters are ignored in the vhost if they are also defined in the main server (i.e. it is useless to define the same <Proxy> with different parameters both in the main server and a vhost :) > The patches proposed so far would not change this. Yes, it implements a score per vhost... On Tue, Aug 25, 2015 at 11:39 AM, Plüm, Rüdiger, Vodafone Group <[email protected]> wrote: > How about the following patch? It uses the server_rec of the server that > originally created the configuration item. LGTM, thanks Rüdiger for helping on this.
