If the upstream refuses to process a request, you might wish to emulate an unavailable service or a lack of response (timeout). Backend up and working are expected to process requests. Switching between legitimate errors and faked one will be done by monitoring backend logs.
There is no such thing as a 'Coffee Break' HTTP code. :oP --- *B. R.* On Thu, Dec 10, 2015 at 9:20 PM, Frank Liu <[email protected]> wrote: > No, 503 may be a legitimate error from upstream that nginx needs to pass > to client. > I am thinking some unused code , say, 590. > > > On Thursday, December 10, 2015, B.R. <[email protected]> wrote: > >> Like... 503? >> To me 'server wants to make another upstream dealing with the request' >> sounds very much like 'Service Unavailable'. >> --- >> *B. R.* >> >> On Thu, Dec 10, 2015 at 5:34 PM, Frank Liu <[email protected]> wrote: >> >>> Hi >>> >>> There are a few options for when to try next upstream : >>> http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_next_upstream >>> >>> Is it possible to configure a custom http code so that upstream servers >>> can send that code if it wants to send nginx to upstream ? >>> >>> Thanks >>> Frank >>> >>> _______________________________________________ >>> nginx mailing list >>> [email protected] >>> http://mailman.nginx.org/mailman/listinfo/nginx >>> >> >> > _______________________________________________ > nginx mailing list > [email protected] > http://mailman.nginx.org/mailman/listinfo/nginx >
_______________________________________________ nginx mailing list [email protected] http://mailman.nginx.org/mailman/listinfo/nginx
