top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

maxConnection and keepAliveTimeout

+1 vote
225 views

If we do not configure "maxConnections" then it will take default value as maxThread (which is 200) and "keepAliveTimeout" will take default value of connectionTimeout (which is 60 seconds) then what is a impact of configuring these parameters?*

What value for "keepAliveTimeout" will be consider as the best?

posted Dec 11, 2015 by Sheetal Chauhan

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button LinkedIn Share Button

Similar Questions
+1 vote

I use apache 2.4 on centos.

I want to protect the access to a page (/my_folder/secure) with a cookie (in my exemple the cookie name is : my_cookie_name)

I would like that some machine with IP 192.1.1.10 and 192.1.1.11 can access the server without the cookie. This two IP address don't need to have the cookie for access to /my_folder/secure)

And all other IP address are redirect to address https://my_register_site.com if they don't have the cookie.

How to write this ? Some example, and of course it does not work.

Session On 
RewriteEngine on 
RewriteCond %{HTTP_COOKIE} !my_cookie_name 
RewriteCond %{REMOTE_ADDR} !^192.1.1.10$ 
RewriteCond %{REMOTE_ADDR} !^192.1.1.11$ 
RewriteRule ^(.*)$ https://my_register_site.com [NC,L,R=301] 
0 votes

I want to allow a directory " /var/www/html/ldap" to two users according to IPs (192.168.1.2 192.168.1.7):

 Order allow,deny
 Allow from 192.168.1.2 192.168.1.7
 Satisfy any
 AuthName "LDAP Authentication"
 AuthType Basic

 AuthBasicProvider ldap
 AuthzLDAPauthoritative off
 AuthLDAPURL ldap://192.168.1.3/dc=example,dc=com?uid?sub?(objectClass=*)
 Require valid-user

but I don't want to allow a sub directory to 192.168.1.7 (I want it to be allowed only to 192.168.1.2):

I have tried to add:

 Order allow,deny
 Allow from 192.168.1.2
 Satisfy any
 AuthName "LDAP Authentication"
 AuthType Basic

 AuthBasicProvider ldap
 AuthzLDAPauthoritative off
 AuthLDAPURL ldap://192.168.1.3/dc=example,dc=com?uid?sub?(objectClass=*)
 Require valid-user

but it seems that 192.168.1.7 can reach to manager directory because it is a part of ldap directory, how can I forbid this?

0 votes

I've an Apache/2.2.15 in front a JBoss Cluster (based on 2 nodes) in which web applications are deployed in HA Singleton mode.

In this case the web applications are always running on a specific node but/and in case of failure the cluster actives them on the other node.

I'd like use Apache ProxyPass, with balancer directives, to refer these web applications, but I need that no requests are sent to the "stand-by" back-end node.

Could you give me some hints about this kind of configurations

The standard balancer configuration should be

 BalancerMember ajp://node1:8009
 BalancerMember ajp://node2:8009

 ProxyPass /web-app1 balancer://SingletonCluster
 ProxyPass /web-app2 balancer://SingletonCluster

but I can't find out the options/parameters that guarantee me the behavior expected

...