| Age | Commit message (Collapse) | Author | Files | Lines |
|
is given by expression and refers to a defined upstream
|
|
patch by Maxim Dounin
the bug has been introduced in r3461
|
|
|
|
a limit_except block if no handler was defined for the block
|
|
|
|
|
|
|
|
delete ngx_http_cache(), ngx_http_no_cache_set_slot()
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
because it is anyway very seldom case
|
|
|
|
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 bug had been introduced in r3461
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
this fixes the erroneous message "upstream prematurely closed connection
while reading response header from upstream"
|
|
internal redirect
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
fastcgi handler, the bug has been introduced in r2444
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|