Thank you very much, Maxim.
I implemented the solution as you advised.
Eran
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,253006,253116#msg-253116
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
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 a
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 callba
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 clien
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 closes it / the server is restarted.
It is true that write_event_handler g
Hello!
On Mon, Sep 01, 2014 at 05:25:56PM -0400, erankor2 wrote:
> 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 erro
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
ngx_http_fi
