1.9.13 and non_idempotent

Frank Liu gfrankliu at gmail.com
Fri Apr 1 15:46:30 UTC 2016

Can you post a quick patch on how to exclude http_404?


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

> Hello!
> 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
> > upstream.
> 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20160401/40f7636e/attachment.html>

More information about the nginx mailing list