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

On 12/04/2011 12:59, Richard Mansfield wrote:

> The lack of support for external servers, in practice, seems to be a
> huge hole in the feature set. A large benefit of FCGI is in being able
> to easily connect custom non-web applications to a webserver for eg.
> providing data for existing web applications.
Exactly, which is what I am doing. I converted my client-server app into =

a web app using fastcgi and it required that I make my own fastcgi =

protocol implementation but at least I don't have to rewrite everything =

else.

This means that support for external servers/TCPIP is pretty important =

like you say.


> Zev, have you been able to trace through the server code and figure
> out what is happening? I looked through fcgi_protocol_dequeue at
> http://www.fastcgi.com/cvs/mod_fastcgi/fcgi_protocol.c and it looks
> correct to me. Perhaps with more information a fix could still be
> applied?

Frankly, it took me 3-4 days of painful debugging just to find the cause =

and then 10 minutes to program a workaround and I didn't feel like =

starting to debug mod_fastcgi code after that. As i said, my workaround =

was to ensure that end packets were never split - everything else worked =

fine. WIthout it, I get an unequivocal 100% cpu freeze on httpd.exe =

every single time.