Add proxy_next_upstream_action to distinguish diffrient network actions

[Shafreeck Sea]

Hi all:

The directive "proxy_next_upstream error timeout" takes effect on three
network actions: connection, send and recieve. In practice ,we realy want
to try next upstream according to in which actions we are. For example, I
do not want to try next upstream if some error occurs or timed out when
recieving response from upstream, otherwise it maybe duplicate my request .

The proxy_next_upstream_action is involved to address this problem , the
directive takes one or more parameter : conn, send, recv which indicates
whether we should try next upstream.

Usage:
proxy_next_upstream error timeout;
proxy_next_upstream_action conn;
Try next upstream if error or timed out on connection.

Anyone suggests ?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20140115/149bce0d/attachment.html>