Bill, not that pages are not showing up, the only problem with
AcceptFilter data has been the AcceptEx error/becoming unresponsive. I
admit to never suggesting trying AcceptFilter connect. Of course, the
problem is on the https side so I never tell them to go to "none" for
https.
I leave mine at the default (data) for https, have a script that
monitors the error log and sends a graceful restart when it detects a
new AcceptEx error. I do not think I have ever recieved a blank/partial
page with the default.
If you have a patch, I'll be glad to patch 2.4 head and try it out.
On 3/15/2012 4:13 AM, William A. Rowe Jr. wrote:
> Gregg, I believe these overrides are either not needed at all, or are
> not needed in specific cases, and have yet to determine which is the
> case that the users are experiencing.
>
> Is anyone complaining about AcceptFilter data or connection? If not,
> then these lines of code simply need to be dodged for AcceptFilter none.
>
> On 3/15/2012 6:06 AM, Gregg Smith wrote:
>> Bill,
>>
>> Us Windows folk would be ecstatic! It is affecting a few noisy users, then there's
the
>> silent masses :)
>> Not sure what APR quirks, refresh my memory.
>> I'm +1 for a APU 1.4.2 also, crypto not building for static lib throws a decent sized
>> monkey wrench into the httpd build. Then maybe we can connect the dots in the .dsw
files
>> and in makefile.win (which you have started sort of).
>>
>> Gregg
>>
>> On 3/14/2012 10:29 PM, William A. Rowe Jr. wrote:
>>> On 3/14/2012 2:36 PM, Jim Jagielski wrote:
>>>> In the attempts to keep the momentum going, I'd like to push for
>>>> a httpd 2.4.2 release Real Soon Now.
>>> Then this afternoon I'll propose a 'really small patch' around
>>> 'the win32 issue' and ask folks who have had problems, and those who
>>> have not, to test it out. It appears MSDN documentation was not our
>>> friend and their directives were misplaced, and the patch should drop
>>> some code (not used back in 2.2) which might be the underlying cause
>>> of Steffan and crew's issues.
>>>
>>> We would probably hear back within the day, so windows folks would
>>> be very happy with a T&R sometime Friday-Monday. I just can't recall
>>> offhand if all the win32 quirks in apr were resolved in 1.4.6, or
>>> a new T&R is still needed on that side?
>>>
>>
>
|