| Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
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
|
|
|
|
|
|
|
|
|
|
this fixes fastcgi_catch_stderr segfault introduced in r1453
*) ngx_http_upstream_hide_headers_hash()
*) proxy/fastcgi pass_header/hide_header use
ngx_http_upstream_hide_headers_hash()
|
|
to go to a next upstream on invalid_header condition
|
|
|
|
|
|
|
|
|