mod_proxy: Status-Flags vs. "Hard-Disabling" for BalancerMembers

Hi all!

I have a short question: What ist the advantage of the 'disabled'-flag
in:

BalancerMember http://1.2.3.5:8080 status=+D route=2

since it would be as easy to disable it with a hash-comment (or strip it
completely):

#BalancerMember http://1.2.3.5:8080 route=2

Sounds more 'safe' to me ;-). Are there any issues with that? (Caching,
active connections, etc..) What's the difference? Or should I use the
'stopped'-flag in addition?
The backend should be disabled for for example maintaining purposes.

Kind regards:
Florian Schröder


------------------------------------------------------------ ---------
The official User-To-User support forum of the Apache HTTP Server Project.
See for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org