| Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
*) refactor ngx_palloc()
*) introduce ngx_pnalloc()
*) additional pool blocks have smaller header
|
|
|
|
nginx did not process FastCGI response if header was at end of FastCGI record
|
|
|
|
|