top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Is it possible to configure Apache 2.4 to accept only one connection at time on port 443?

+1 vote
369 views

Is it possible to configure Apache 2.4 to accept only one connection at time on port 443? is this something I can configure for my Virtual Hosts?

posted Feb 18, 2016 by anonymous

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

Similar Questions
+2 votes

Is it possible to use PHP 5.2.5 with Apache/2.4.6?

I have an application that was written in WAMP5 using PHP 5.2.5, and I am trying to get the application onto a CentOS server and I can't get it to work with 5.4.16.

Are there any good tutorials on using an older version of PHP with Apache?

+2 votes

I updated my Server from Apache 2.2 to Apache 2.4 ( windows binaries from apachehaus on Windows Server 2008 x86)

The configuration is the same. Only the necessary syntax changes were made.

I have a test repository with the same content over the past 8 years. Before and after each change of a configuration I measure the time consumed for checking out this repository.

The old configuration with Apache 2.2 and SVN 1.8.11 needed 22 seconds. With Apache 2.4 it lasts about 180 seconds.

Does anybody have an idea what has changed or what has to be changed?

+1 vote

I am facing the issue while building apache on Window machine with the help of apache source code and got below error

[ 92%] Building C object CMakeFiles/mod_ssl.dir/modules/ssl/ssl_engine_init.c.obj 
ssl_engine_init.c 
C:apacheBuildapache2.4buildhttpd-2.4.33modulessslssl_engine_init.c(33) : fatal error C1083: Cannot open include file: 'mod_md.h': No such file or directory 
NMAKE : fatal error U1077: 'c:PROGRA~2MICROS~2.0VCbinamd64cl.exe' : return code '0x2' 
Stop. 

I did some investigation and found that with new version of apache we added a new module called MOD_MD which is experimental basis, I don't know why experimental module added as a dependency and it will cause a build failure,

Can you please help me out to fix above issue?

+1 vote

Just set up a FreeBSD jail to run httpd in it and all works good except these two, rewrite/proxy modules.

These are error logs excerpts:

MOD_REWRITE error: 
[rewrite:crit] [pid 43447] (13)Permission denied: AH00666: mod_rewrite: could not init rewrite_mapr_lock_acquire in child 
MOD_PROXYÂ error: 
[proxy:crit] [pid 43447] (13)Permission denied: AH02479: could not init proxy_mutex in child 

Not sure permissions of what are being denied as html in document root is being served just fine when these modules are disabled.

I tried googling but found nothing but rubbish. Please help?

0 votes

We are currently using HTTP connector in tomcat 7.42 and planning to switch to AJP NIO connector. When I was reading through the docs I found "WARNING: The NIO connector for AJP is experimental."

This made me think that NIO connector might not be mature at this point. Can somebody who had experience with NIO connector let me know if it is stable and any pitfalls I should be aware of?

Stable enough to be used on enterprise apps which is expected to get thousands of requests in a hour?

Any information would be helpful.

...