Keep Server Online|
If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.
A donation makes a contribution towards the costs, the time and effort that's going in this site and building.
Thank You! Steffen
Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
| Topic: Apache 2.4.1 Win32 & 64 available
Joined: 15 Oct 2005
Location: Hilversum, NL, EU
|Posted: Wed 15 Feb '12 14:01 Post subject: Apache 2.4.1 Win32 & 64 available
|Be aware that this is fairly new. For the latest stable, download the proven Stable 2.2.22 version.
For a known issue with SSL, see below.
6 March 2012:
Build with VC10, we keep supplying VC9 Win32 builds at the Additional download page.
1 March 2012:
APR fix for Win64, see Changelog.
Documentation: http://httpd.apache.org/docs/2.4/ attention there to Upgrading to 2.4 from 2.2
The issue which already reported by me back in June 2011, did not had the wright attention from ASF and was ignored. Now it is too hard for them to solve it in time for GA. I feel that it has still not high priority at the ASF and are not going out there to get help from others, like Microsoft and/or Network card vendors.
Not all configurations are dealing with the issue, some has no problems at all.
So always worth to try if it works with your configuration.
When you get for example in your log: winnt_accept: Asynchronous AcceptEx failed.
Then probably you are dealing with the issue.
The SSL issue is caused by the new directive AcceptFilter which replaces the 2.2 one Win32DisableAcceptEx.
1. AcceptFilter https data [default] + mod_ssl works, except when it doesn't - those users who previously in 2.2 had to use DisableWin32AcceptEx.
2. AcceptFilter https none/connect + mod_ssl can fail due to timing sensitive retry problems which cause ssl connections to intermittently fail. How intermittent is a timing side effect of browser and server.
For non SSL traffic the AcceptFilter http none/data/connect works as expected.
To overcome and enjoy the goodies from 2.4: I have a 2.2.22 SSL-only with Reverse Proxy in front of 2.4. A minimal httpd.conf with eg. only mod_ssl, mod_proxyx and logging loaded. And no vhosts. Running already for months here.
It feels an advantage in general, it offloads recources from the high non-SSL traffic. Kinda extra multi-threaded.
ProxyPass / http://127.0.0.1/
ProxyPassReverse / http://127.0.0.1/
See also the discussion for more insight: http://www.apachelounge.com/viewtopic.php?t=4461
Last edited by Steffen on Tue 21 Feb '12 13:01; edited 3 times in total
|Back to top