Hi All,
I am trying to setup a hot cluster with following configuration.
VirtualHost *:8787
ServerName http://in-g-vsinha4
ServerAlias in-g-vsinha4.com
ProxyPass / balancer://hotcluster/
Proxy balancer://hotcluster
On 31/03/2014 5:20 PM, Sinha, Vikas vikas.si...@intergraph.com wrote:
Hi All,
I am trying to setup a hot cluster with following configuration.
VirtualHost *:8787
ServerName http://in-g-vsinha4
ServerAlias in-g-vsinha4.com
ProxyPass /
Thanks a lot!
I've made a hack which puts the suspeded connection back in the queue:
https://gist.github.com/ArtemGr/9887564
with that the test case works! (`ab` no longer timeouts).
Would it make sense to submit a feature request along these lines?
Should I make a patch or leave it to the more
Please open a bug
for the issue. trunk also has a facility to get called back when a
socket is readable, mod_proxy_wstunnel uses it. It really needs a timeout
to be useful.
What are the system overhead considerations when creating a Deny from
someipaddress
What about long list of those? Is there some sort of tipping point?
I cannot find it now, but I recall reading recently that Rewrite, while
powerful, is demanding on system resources.
If you were to use Rewrite is a method for dynamic virtual hosting on a large
number of sites, could that cause a significant problem on system performance
compared to mod_vhost,