> No, this is not how it works: nginx never use "Expect:
> 100-continue" on requests to backends. It is, however, smart
> enough to stop sending the body as long as the backend server
> responds with an error, so (almost) no bandwidth is wasted.
Yeah, that's my fault. I left "proxy_set_header Expe
Hello!
On Sat, May 01, 2021 at 12:38:30AM -0400, kbolino wrote:
> Use case: Large uploads (hundreds of megabytes to tens of gigabytes) where
> nginx is serving as a reverse proxy and load balancer. The upstream servers
> can get bogged down, and when they do, they apply backpressure by responding
Use case: Large uploads (hundreds of megabytes to tens of gigabytes) where
nginx is serving as a reverse proxy and load balancer. The upstream servers
can get bogged down, and when they do, they apply backpressure by responding
with 503 status code.
Problem: Naively implemented, the client sends t
