----- Original Message ----- > You can't select something similar on GUI, but If you have to > maintenance all your backends on the same time you can obtain the > same result if you personalize your HTTP messages errors, with some > HTML web. > It will be implemented on new releases. > > Like a workaround: If you have to maintenance only one backend on > your farm, YOu can modify the backend port on the farm > configuration.
For now I only have one backend server, which is why I would like ZLB to work as a failover configuration. I will see if I can use the HTTP error messages instead. > By default HTTP/HTTPS works with weight algorithm (the same weight > for all backends) more information about this on web documentation: > > http://www.zenloadbalancer.com/doc/ZenLB%20administration%20guide.html#__RefHeading__643_521824990 > > "By contrast with the TCP or UDP farms profile, the HTTP/HTTPS > profile use a weight algorithm implicitly." Okay. > It isn't possible on any profile, zen at the moment works in sNAT > method, backends only know the load balancer IP Right, but we can use the X-Forwarded-For header which should be included with client requests when using a HTTP/HTTPS farm. -- Best regards Jeppe Toustrup ------------------------------------------------------------------------------ 10 Tips for Better Server Consolidation Server virtualization is being driven by many needs. But none more important than the need to reduce IT complexity while improving strategic productivity. Learn More! http://www.accelacomm.com/jaw/sdnl/114/51507609/ _______________________________________________ Zenloadbalancer-support mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
