On 2019-05-21 00:28, NginxNewbee wrote:
> Hey Maxim, can you please find some time to respond to my last question. We
> read nginx code as well on git hub but confusion remains. We would really
> appreciate your help on it.
If you need immediate help, a support contract or nginx consultant is
prob
Hey Maxim, can you please find some time to respond to my last question. We
read nginx code as well on git hub but confusion remains. We would really
appreciate your help on it.
Thanks !
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,284214,284225#msg-284225
_
Thanks. Your understanding is correct. For cases, when
ngx_http_read_client_request_body returns NGX_AGAIN, thread returns and
request will get finalized. I'll go ahead and move reading contents of r and
request body to main thread in the content handler and just keep execution
of our business logi
Hello!
On Mon, May 20, 2019 at 03:04:05PM -0400, NginxNewbee wrote:
> Thanks for your comments, Maxim. I truly appreciate it.
>
> For first comment, the reason I chose to do request processing on thread is
> so it wouldn't block nginx. We launch one thread per request (from content
> handler). T
Thanks for your comments, Maxim. I truly appreciate it.
For first comment, the reason I chose to do request processing on thread is
so it wouldn't block nginx. We launch one thread per request (from content
handler). There will never will be multiple threads working on a request. r
is passed onto
Hello!
On Sat, May 18, 2019 at 05:10:29PM -0400, NginxNewbee wrote:
> Apologies if this is a trivial question. I have searched it on web and none
> of the answers have solved my problem. I am trying to read request body and
> thing seem to work fine if request body is small (4 kb). As soon as it
