comparison src/http/modules/ngx_http_uwsgi_module.c @ 5231:05c53652e7b4

Upstream: http_403 support in proxy_next_upstream (and friends). The parameter is mostly identical to http_404, and is expected to be used in similar situations. The 403 code might be returned by a backend instead of 404 on initial sync of new directories with rsync. See here for feature request and additional details: http://mailman.nginx.org/pipermail/nginx-ru/2013-April/050920.html
author Maxim Dounin <mdounin@mdounin.ru>
date Mon, 27 May 2013 16:54:09 +0400
parents 8da37c1b22a4
children 1a070e89b97a
comparison
equal deleted inserted replaced
5230:2139768ee404 5231:05c53652e7b4
76 { ngx_string("error"), NGX_HTTP_UPSTREAM_FT_ERROR }, 76 { ngx_string("error"), NGX_HTTP_UPSTREAM_FT_ERROR },
77 { ngx_string("timeout"), NGX_HTTP_UPSTREAM_FT_TIMEOUT }, 77 { ngx_string("timeout"), NGX_HTTP_UPSTREAM_FT_TIMEOUT },
78 { ngx_string("invalid_header"), NGX_HTTP_UPSTREAM_FT_INVALID_HEADER }, 78 { ngx_string("invalid_header"), NGX_HTTP_UPSTREAM_FT_INVALID_HEADER },
79 { ngx_string("http_500"), NGX_HTTP_UPSTREAM_FT_HTTP_500 }, 79 { ngx_string("http_500"), NGX_HTTP_UPSTREAM_FT_HTTP_500 },
80 { ngx_string("http_503"), NGX_HTTP_UPSTREAM_FT_HTTP_503 }, 80 { ngx_string("http_503"), NGX_HTTP_UPSTREAM_FT_HTTP_503 },
81 { ngx_string("http_403"), NGX_HTTP_UPSTREAM_FT_HTTP_403 },
81 { ngx_string("http_404"), NGX_HTTP_UPSTREAM_FT_HTTP_404 }, 82 { ngx_string("http_404"), NGX_HTTP_UPSTREAM_FT_HTTP_404 },
82 { ngx_string("updating"), NGX_HTTP_UPSTREAM_FT_UPDATING }, 83 { ngx_string("updating"), NGX_HTTP_UPSTREAM_FT_UPDATING },
83 { ngx_string("off"), NGX_HTTP_UPSTREAM_FT_OFF }, 84 { ngx_string("off"), NGX_HTTP_UPSTREAM_FT_OFF },
84 { ngx_null_string, 0 } 85 { ngx_null_string, 0 }
85 }; 86 };