Re: Debugging help: POSTs, SSL, mod_fastcgi, and PHP5

David Birnbaum <[email protected]>
Newsgroups gmane.comp.web.fastcgi.devel,gmane.spam.detected
Message-ID <[email protected]>
Garrett,

Are you sure this is a FastCGI problem?  Older versions of IE had 
problems with SSL sessions running http 1/1 with keep-alive.  I believe 
you need to disable that feature or you will see (and the end user will 
see) errors.  I can't recall the exact nature of the bug, but it might 
be worth checking out.  FastCGI happens after all of the SSL 
negotiation, so I'd expect that this is a problem at the SSL layer, not 
the FastCGI layer.

David.

------------------------------------------------------------------------

Garrett Wollman wrote:
> We have a bunch of Debian etch Web servers, all running Apache 2.2 and
> mod_fastcgi (from the apache2.2 and libapache2-mod-fastcgi packages),
> and I'm having an odd problem with POSTs not working properly for
> SSL-protected, certificate-authenticated PHP5 pages.  (We have PHP4 as
> an Apache module for legacy-support reasons, and we're trying to use
> mod_fastcgi to run PHP5 applications.)  I straced php5-cgi (which was
> started by Apache using FastCgiServer) and found that it was hanging
> waiting for mod_fastcgi to transmit the POST data.  Eventually, a
> timer expires and mod_fastcgi closes the connection, with a log
> message like the following:
>
> [Thu Oct 25 17:42:44 2007] [error] [client 128.30.28.20] FastCGI: incomplete headers (0 bytes) received from server "/usr/bin/php5-cgi", referer: [deleted]
>
> Any suggestions on how to go about debugging this?
>
> -GAWollman
>
> ___________________________________
> fastcgi-developers mailing list
> http://fastcgi.com/fastcgi-developers/
>

___________________________________
fastcgi-developers mailing list
http://fastcgi.com/fastcgi-developers/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.