Re: Possible serious bug in mod_fastcgi-2.4.6-AP22.dll

Mrjk <[email protected]> Tue, 12 Apr 2011 10:33:49 +0100
Newsgroups gmane.comp.web.fastcgi.devel
Message-ID <[email protected]>
Hi, I think you should report this bug on the official Apache mailing list =
...

Best regards,
--
MrJK



2011/4/12 Zev Toledano <[email protected]>:
> OK I did my part. I guess this project isn't as alive as I thought....
>
>
>
> On 05/04/2011 18:54, Zev Toledano wrote:
>
>> Greetings,
>>
>> I need to report a possible serious bug but can't find any way to do this
>> except via this mailing list. Apologies if I am doing this wrong:
>>
>> I have developed my own Windows FastCGI app that uses its own FastCGI
>> protocol implementation, and it depends on
>> Apache2+mod_fastcgi-2.4.6-AP22.dll to run it.
>>
>> I recently noticed that httpd.exe sometimes stops responding and takes
>> 100% cpu until it is killed.
>>
>> After MUCH debugging, I found the cause:
>>
>> Sending an FCGIEndRequest(3) packet header in pieces. Specifically, If I
>> send the first two bytes of the packet separately, and then the rest, it
>> causes the 100% cpu issue. This happens because I send the complete resp=
onse
>> in batches of 4096 and sometimes the packet headers become split.
>>
>> Can anyone confirm this or tell me where to report bugs and what to do
>> next?
>>
> _______________________________________________
> FastCGI-developers mailing list
> FastCGI-developers-xGejAJT2w6xVgU18Zptdi0EOCMrvLtNR@public.gmane.org
> http://mailman.pins.net/mailman/listinfo.cgi/fastcgi-developers
>