httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gregg L. Smith" <>
Subject Re: Windows 2.3.13 :: Win32DisableAcceptEx
Date Fri, 30 Sep 2011 01:24:25 GMT

I think it's been realized that the APR/IPv6 has no bearing on this but 
I can confirm that
2.3.15-dev at r1177210 with apr 1.4.2 and ipv6 set to 0 does the exact 
same thing.



On 9/29/2011 11:58 AM, William A. Rowe Jr. wrote:
> On 7/7/2011 3:39 AM, Gregg L. Smith wrote:
>> I have an error log full of these;
>> [Thu Jul 07 00:15:58.010625 2011] [mpm_winnt:warn] [pid 2840:tid 1572] (OS 64)The
>> specified network name is no longer available.  : winnt_accept: Asynchronous AcceptEx
> This might be
> confusing the issue if you build with Win32 IPv6 toggled on, depending on
> your operating system and the SDK you used to build... it was introduced
> in 1.4.3, you might want to try reverting this patch after first working
> through the ticket below...
>> Thanks to Steffen's bringing this up, I now know how I should be fixing this.
>> The problem is, if I set
>> AcceptFilter http none
>> I lose all my vhosts and everything reverts to the main host. If I use
> Implies that the host headers are not queried for ***normal*** sockets,
> and reviewing
> it looks like this was "optimized" (read:bugged) away.
> Could you please revert this APR 1.4.3 change and report back what you
> observe?  Another option is to simply try APR 1.4.2 binaries.
> It seems AcceptEx() crap still pollutes APR.  We can't optimize for the
> AcceptEx() case because that is handled in httpd.  The flag simply prevents
> us from querying twice (and this becomes stranger because getpeername()
> simply fails for an AcceptEx'ed socket anyways).  The unknown flag can only
> be tripped if we can affirmatively set the correct value.

View raw message