I should have added -- I know that there are 60 second (default)
timeouts in place so if nginx cannot write upstream for 60 seconds it
will abort the request. That's fine; it's the shorter scenarios I am
worried about. In fact, what happens when nginx doesn't send the
remaining data in my case
The POST payload varies but can be as much as 20M
nginx and the upstream are in the same data center now, but that isn't
necessarily a requirement, and even in the data center speeds will vary
depending on network congestion. Hence I cannot guarantee the worst-case
latency. If the upstream jav
I have an nginx proxy through which clients pass a large POST payload to
the upstream server. Sometimes, the upstream server is slow and so
writing the POST data will fail with a writev() not ready (EAGAIN)
error. But of course, that's a very common situation when dealing with
non-blocking I/O,
