1.9.13 and non_idempotent
mdounin at mdounin.ru
Wed Mar 30 03:26:30 UTC 2016
On Tue, Mar 29, 2016 at 08:04:33PM -0700, Frank Liu wrote:
> It's a custom error code, think of it as if http_404, so if the first
> upstream can't handle this request , it will send "404" saying it is not
> for me, please try next, nginx should then send the same request to next
Well, nginx can't handle custom error codes in
proxy_next_upstream, so this is probably irrelevant anyway.
Though I was considered excluding http_403 and http_404 from
idempotence checks, it may make sense to do it if there are enough
such use cases.
> On Tuesday, March 29, 2016, 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.
> > > For other http code, I like the idea of not retry if it is non
> > > idempotent but for one http_xxx, I want retry no matter what type of
> > > request.
> > Just curious - which one?
> > Note well that if you want finer control of how various HTTP errors are
> > handled, you can use proxy_intercept_errors with appropriate
> > error_pages configured. See http://nginx.org/r/proxy_intercept_errors.
> > --
> > Maxim Dounin
> > http://nginx.org/
> > _______________________________________________
> > nginx mailing list
> > http://mailman.nginx.org/mailman/listinfo/nginx
> nginx mailing list
> nginx at nginx.org
More information about the nginx