1.9.13 and non_idempotent

Frank Liu gfrankliu at gmail.com
Fri Apr 1 02:46:40 UTC 2016

Does that mean by default if one upstream server is down (connect error or
connect timeout), nginx won't try the next server and POST request will
just fail?


On Tue, Mar 29, 2016 at 7:48 PM, Maxim Dounin <mdounin at mdounin.ru> wrote:

> Hello!
> On Tue, Mar 29, 2016 at 06:34:59PM -0700, Frank Liu wrote:
> > If I explicitly configured to retry next upstream based on a
> > certain http_xxx, will that stop working if a request is a POST with
> > 1.9.13?
> Yes.  There is no real difference between a network error and an
> HTTP error returned from idempotence point of view.  E.g., 502
> error just means that a network error happened somewhere else.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20160331/54cbbbca/attachment.html>

More information about the nginx mailing list