Frank Liu gfrankliu at
Thu Mar 3 03:55:21 UTC 2016

Does the proxy_next_upstream "timeout" apply to both connect timeout and
read timeout?
Is it possible to configure proxy_next_upstream to use connect timeout
only, not the read timeout? In case a connection is made and the request is
sent, I don't want to re-try next upstream even when the read timeout
happens. Retry in this case could cause damage to the upstream (duplicate
payment, etc).

Can someone also give some example of "error" or "invalid_header"? Are they
100% safe, meaning not causing upstream to process the request twice? Am I
right that the only real safe is the connect timeout?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the nginx mailing list