Bug #990
closedproxy-core.balancer should not be mandatory
Description
It should not be mandatory to include proxy-core.balancer in the configuration file if mod_proxy_core is loaded, especially if you only have one back end. It should assume a default value.
If you omit it, the following error occurs:
/root/lighty/trunk/src/mod_proxy_core.c.298: (error) proxy.balance has to be on of 'round-robin', 'carp', 'sqf' got (null)
Updated by Anonymous about 18 years ago
I'd like to see a {{{proxy-core.balancer: none}}} as well, both for single-backend proxies and 'hidden' proxies controlled by X-Rewrite-Backend.
When I provide X-Rewrite-Backend: host123 and that host is down, I never want the balancer to attempt another backend. A 'none' balancer would ensure that.
-- Jeremy Kemper <jeremy
Updated by jan about 18 years ago
- Status changed from New to Fixed
- Resolution set to fixed
fixed in r1529, we use round-robin as default. If there is only one backend available it is just ignored.
Also available in: Atom