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]> |
Hmmm...well, its going to be tough to debug unless you can reproduce it. We don't run Apache 2 here, but if you can get a truss/strace of the httpd process talking to the FastCGI application when it fails, that would probably be very illuminating (and easier than attaching with gdb). Are there any other log messages that show up? A tcpdump at the same time would allow you to trace through the network write() to the FastCGI write and see where the POST data is getting lost/dropped. Otherwise, you'd have to instrument that Apache and/or mod_fastcgi code, which has issues of it's own, of course. David. ------------------------------------------------------------------------ Garrett Wollman wrote: > <<On Fri, 26 Oct 2007 09:12:17 -0400, David Birnbaum <[email protected]> said: > > >> 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 don't use IE, and I know that other (non-FastCGI) applications work > correctly. (In fact, we've observed a different issue there, because > Apache 2 limits the amount of POST data an SSL connection may have in > certain circumstances, so we know POST-over-SSL does work up to that > limitation with regular CGI and with embedded PHP4.) > > -GAWollman > > ___________________________________ fastcgi-developers mailing list http://fastcgi.com/fastcgi-developers/