_upstream_max_fails and _upstream_fail_timeout directives

[Igor Sysoev]

On Wed, May 19, 2010 at 11:17:13PM +0200, Manlio Perillo wrote:

> Igor Sysoev ha scritto:
> > On Wed, May 19, 2010 at 01:15:43PM +0200, Manlio Perillo wrote:
> > 
> >> Hi.
> >>
> >> Starting from Nginx 0.5.0, the directives "proxy_upstream_max_fails",
> >> "proxy_upstream_fail_timeout", "fastcgi_upstream_max_fails",
> >> "fastcgi_upstream_fail_timeout", "memcached_upstream_max_fails", and
> >> "memcached_upstream_fail_timeout" are no more supported.
> >>
> >> However they are still supported in the code.
> >> What is the reason?
> > 
> > Because
> > 
> >     *) Feature: the "server" directive in the "upstream" context supports 
> >        the "max_fails", "fail_timeout", and "down" parameters.
> > 
> > They conflicted.
> > 
> 
> What I meant was: "why the directives are still defined in the source
> code for the proxy, fastcgi and memcached modules".
> 
> If they are no more supported, I'm not sure to understand why they are
> still defined (and just raise an error message).

I usually keep old directives for two and so version branches to help
migration from old nginx versions. However, these directives lived too
long, I will remove them in the next 0.8.38. Thank you.


-- 
Igor Sysoev
http://sysoev.ru/en/