| Age | Commit message (Collapse) | Author | Files | Lines |
|
fastcgi_upstream_max_fails, fastcgi_upstream_fail_timeout,
memcached_upstream_max_fails, and memcached_upstream_fail_timeout
directives obsolete since 0.5.0 version
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
*) the indexed variables are always flushed
*) never show warning for not found variables
|
|
|
|
|
|
|
|
|
|
|
|
|
|
if 400 or 414 response has been redirected to upstream
|
|
|
|
|
|
the bug had been introduced in r3461
|
|
|
|
|
|
|
|
and does not begin at /16 network boundary
|
|
|
|
instead of default one
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
frequent here: 304 and HEAD responses are not set it before the filter
|
|
|
|
|
|
|
|
|
|
|
|
|
|
for non-mulitiplicity perl
|
|
|