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

<<On Fri, 26 Oct 2007 14:05:57 -0400, Matt Marcella <[email protected]> said:

> I am not sure what it is worth, but we use Apache 2 and SSL certs (along 
> with mod_auth) and it works fine.

You probably won't see this problem unless you use per-directory SSL
configuration, which results in connection renegotiations.  (And even
then, you won't see it every time due to caching effects and/or
SSLOptions OptRenegotiate.)

I think I have made some progress in tracking this down.  mod_fastcgi
uses an obsolete Apache interface, ap_get_client_block(), to read the
client's POST data.  mod_cgi uses the new (Apache 2.x) "bucket
brigade" interfaces, which seems to work correctly (whereas the
ap_get_client_block() code does not despite looking very similar).  I
think making mod_fastcgi use the new interfaces would improve
performance, if nothing else, and might actually solve the problem
that I'm having.  On Monday, I'll see how hard it would be to make
read_client_from_n_queue() look more like cgi_handler()'s client read
loop.  (This would also have the bonus that the standard "http_in"
input filter automatically handles "chunked" transfer-encoding and
other unpleasantness that mod_fastcgi currently punts on.)

-GAWollman
___________________________________
fastcgi-developers mailing list
http://fastcgi.com/fastcgi-developers/