On Fri, May 15, 2020 at 11:09:53PM -0400, allenhe wrote:
Hi there,
> w.r.t. the "http://nginx.org/r/proxy_buffering";, the doc does not mention if
> the buffering works for header, body or both,
It's "the response".
It sounds like it should be fairly straightforward to test on your setup,
if yo
Hi Francis,
Thanks for the reply!
w.r.t. the "http://nginx.org/r/proxy_buffering";, the doc does not mention if
the buffering works for header, body or both, I'm wondering if nginx can
postpone the sending of upstream header in any ways? otherwise the client
will get wrong status code in this case
On Fri, May 15, 2020 at 01:51:13AM -0400, allenhe wrote:
Hi there,
> Will nginx buffer the header before receiving of the whole body?
> If not, what if error happens in the middle of body receiving? nginx has no
> chance to resend the error status then.
What do you want your nginx to do, in that
Will nginx buffer the header before receiving of the whole body?
If not, what if error happens in the middle of body receiving? nginx has no
chance to resend the error status then.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,287990,288039#msg-288039
I understand the nginx would proxy the header first and then the body, in
the case the connection with the upstream is broken during the transfer of
body, what status code the client would get? since the nginx would proxy the
200 OK from upstream first to the client, but will nginx send another 5xx
