Thank you very much Maxim ! this works !
However, I bumped into a new problem, I use 2 different types of asyncronous
operations in my code - file I/O and http requests. When I call
ngx_http_run_posted_requests from the aio callback it works well, but when I
call it from the HTTP completion
Hello!
On Thu, Sep 04, 2014 at 04:38:41PM -0400, erankor2 wrote:
Thank you very much Maxim ! this works !
However, I bumped into a new problem, I use 2 different types of asyncronous
operations in my code - file I/O and http requests. When I call
ngx_http_run_posted_requests from the aio
Hello!
On Wed, Sep 03, 2014 at 10:10:01AM -0400, erankor2 wrote:
Maxim, thank you very much for your response.
To clarify - the problem is not about freeing the request (I don't think
there's a resource leak here), the problem is that the connection is just
left hanging until the client
Hi all,
In the module I'm developing, I have the possibility of encountering an
error after the response headers were already sent. As the headers were
already sent (with status 200) the only way for me to signal the error to
the client would be to close the connection. I tried calling
