Hello!
On Fri, Jul 10, 2020 at 09:40:52AM -0700, Frank Liu wrote:
> If you read the same RFC, section 6.5, right before the section you
> mentioned, you can see:
>
>A client sending a message body SHOULD monitor the network connection
>for an error response while it is transmitting the r
Hi,
If you read the same RFC, section 6.5, right before the section you
mentioned, you can see:
A client sending a message body SHOULD monitor the network connection
for an error response while it is transmitting the request. If the
client sees a response that indicates the server does
Hello!
On Wed, Dec 18, 2019 at 10:09:56AM -0800, Frank Liu wrote:
> 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
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 Do
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
Hi,
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
