On Mon, Mar 15, 2010 at 08:56:11PM +0800, ä»»æ™“ç£Š wrote:
On Mon, Mar 15, 2010 at 5:49 PM, Maxim D. [email protected] wrote:
Thank you, Maxim. The document above tells me the detail. I thought
the protocol is a couple of stdio pipes before read this.
So, could you tell me why I see 502 when something in FastCGI’s
stderr? Does texts from FastCGI’s stderr lead to 502 ? But the specs
says they’re just application-level errors.
Writing to stderr shouldn’t lead to 502 from nginx. This may
happen in two cases:
Application actually dies (or aborts request) after writing to
Bug in nginx. There is one known bug with fastcgi_cache and
large stderr from fastcgi apps which may lead to 502 returned
unexpectedly. It’s mostly fixed in 0.8.34, though fix may lead to
segfaults in nginx worker when fastcgi_cache isn’t used, patch is