…d a response header with a different status code has already been sent (but an error message will still be printed into the error.log file). this change makes Lua code debugging based on ngx.say/ngx.print much easier. thanks Matthieu Tourne for the suggestion.
…and the response header was already sent. thanks Kindy Lin for reporting this issue.
…er (\0) in it. thanks Wang Xi for reporting this issue.
…hen removing the 21st request headers. thanks Umesh Sirsiwal for reporting this issue in github issue #176.
…lso to explicitly discourage the use of it.
…ngx.req.socket() finishes reading the whole body.
…in memory leaks; now it returns an error upon subsequent calls.
… ngx.on_abort() and there was no client abort event at all. also ensured that the on_abort callback will not get called when the request is already done.
…request time out) or N = 499 (client closed request) or N = -1 (error). feature: added ngx.on_abort() for registering user Lua function callback which will get called automatically when client abortion happens.
…_upstream_test_connect function of the nginx core.
… testing mode because nginx does not really support the one-way shutdown on the client side.
… might lead to segmentation faults.
…out kqueue, which was introduced by commit 9205848.
…ike "connection refused" when kqueue was used. tests: fixed the compatibilty issues in those test cases that were failing on non-Linux systems like FreeBSD.
…w changes in Test::Nginx::Socket.
…rted" in case request body truncation even when lua_on_client_abort is "ignore". bugfix: for edge-triggered events, use of ngx.req.socket() might prevent "lua_on_client_abort stop" from detecting the connection shutdown event.
…when the request body got truncated; now we return the "closed" error (or "client aborted" when lua_on_client_abort is not configured as "ignore"). feature: implemented new config directive lua_on_client_abort which (atm) takes two possible values, "ignore" (the default) and "stop".