So far I have two reports that mod_ssl is given issues.
Strange, I tried it on three XP boxes and all is fine.
The report is:
error c0000005 at 6FD0F220 (mod_ssl).
c0000005 is 'access violation'.
Using FileMon, this appears to get triggered when trying to read in a server
certificate. I removed the SSL portion of one virtual host and it then
errored in trying to read the certificate for the first virtual host.
Removing both SSL virtualhost portions allows the server to run fine. The
configuration was copied in whole from a working 2.2.0 install
Steffen
----- Original Message -----
From: "William A. Rowe, Jr." <[EMAIL PROTECTED]>
To: <dev@httpd.apache.org>
Sent: Friday, April 07, 2006 11:55
Subject: Re: [VOTE] Release 2.2.1 as GA
Jorge Schrauwen wrote:
Compiler: Visual Studio .net 2005 Pro (out of box, no aditianal SDK's)
FWIW, I'm focused on the Win64 fixes on trunk, backporting compatible
changes to 2.2, and ignoring 2.0 for Win64.
Of course you don't need any SDK's - they are included. For VS 6.0 users
their headers are too far out of date. Studio .Net 2003/2005 users should
certainly not need any updates.
Actually someone just complained about not building correctly the apu ldap
headers. That's not a surprise if using an old VC6 and stale headers.
