Oct 29, 2009, 4:56 AM
Post #2 of 2
For anyone that cares, the cause of this problem is that if the
Re: [RichardJones] Status codes on PerlResponseHandler
[In reply to]
bit includes any "print" statements to STDOUT, anywhere at all in the stack of subsequently executed code, then the response handler sends a 200 header to the browser long before it flushes the request object and its actually desired header back to the client.
So if you have, for example, a logger which logs to STDOUT under certain conditions, it will break your website.
Seems like a bug to me.