I'll second the "config reload" going around...
I would also add a request to be able to define clusters or such of
servers....
An example of this would be like:
Cluster
Name PROD
BackEnd
Address 192.168.1.20
Port 80
End
BackEnd
Address 192.168.1.21
Port 80
End
End
Cluster
Name TEST
BackEnd
Address 192.168.1.22
Port 80
End
BackEnd
Address 192.168.1.23
Port 80
End
End
... later in the config file ...
Service
URL "^/something.*"
HeadRequire "Host:.*blah.something.edu.*"
BackEndCluster PROD
End
Service
URL "^/bork.*"
HeadRequire "Host:.*bork.something.edu.*"
BackEndCluster PROD
End
Service
URL "^/.*"
HeadRequire "Host:.*foo.edu.*"
BackEndCluster TEST
BackEnd
Address 192.168.1.26
Port 80
End
# Would end up sending to 1.22 1.23 and 1.26 (cluster + local
defined)
End
etc.. etc...
That would make maintaining backend server pools/clusters VASTLY easier.
Thanks for considering!
On 12/30/2011 09:44 AM, Robert Segall wrote:
Hallo everybody
New year, new version: we declare open the wish-list for 2.7 features.
Please reply to this with your list of enhancements/patches/wishes.
Please feel also free to offer comments (supportive or not, as the case
may be) on items that others may post. The more support for a feature,
the better its chances of making it into 2.7.
Please do NOT post patches in reply - a short description is quite
enough. You can mail me directly if you want to offer patches.
--
Todd Freeman Ext 6103 .^. Don't fear the penguins!
Programming Department /V\
Andrews University // \\ http://www.linux.org/
http://www.andrews.edu/~freeman/ /( )\ http://www.debian.org/
^^ ^^
--
To unsubscribe send an email with subject unsubscribe to [email protected].
Please contact [email protected] for questions.
