Welcome! Log In Create A New Profile

Advanced

Re: proxy module handling early responses

Frank Liu
December 18, 2019 01:12PM
Our upstream returns HTTP/413 along with "Connection: close" in the header,
then closes the socket. It seems nginx catches the socket close in the
middle of sending the large payload. This triggers additional 502 and
client gets both 413 and 502 from nginx.

On Wed, Dec 18, 2019 at 7:22 AM Maxim Dounin <mdounin@mdounin.ru> wrote:

> Hello!
>
> On Tue, Dec 17, 2019 at 06:37:58PM -0800, Frank Liu wrote:
>
> > When using nginx as a reverse proxy, in case of a large POST payload,
> what
> > does nginx do when upstream server sends response before nginx finishes
> > posting the full payload?
> >
> > One use case is upstream enforces some payload limit and sends a HTTP/413
> > response when the payload read reaches certain limit. Will nginx catch
> this
> > error, stop sending further, and return the 413 to client?
>
> Exactly.
>
> --
> Maxim Dounin
> http://mdounin.ru/
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

proxy module handling early responses

Frank Liu December 17, 2019 09:40PM

Re: proxy module handling early responses

Maxim Dounin December 18, 2019 10:22AM

Re: proxy module handling early responses

Frank Liu December 18, 2019 01:12PM

Re: proxy module handling early responses

Maxim Dounin December 18, 2019 02:38PM

Re: proxy module handling early responses

Frank Liu July 10, 2020 12:42PM

Re: proxy module handling early responses

Maxim Dounin July 13, 2020 11:48AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 86
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready