Mercurial > hg > nginx-vendor-current

comparison CHANGES @ 276:c5c2b2883984 NGINX_0_5_8

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
nginx 0.5.8 *) Bugfix: a segmentation fault might occur if "client_body_in_file_only on" was used and a request body was small. *) Bugfix: a segmentation fault occurred if "client_body_in_file_only on" and "proxy_pass_request_body off" or "fastcgi_pass_request_body off" directives were used, and nginx switched to a next upstream. *) Bugfix: if the "proxy_buffering off" directive was used and a client connection was non-active, then the connection was closed after send timeout; bug appeared in 0.4.7. *) Bugfix: if the "epoll" method was used and a client closed a connection prematurely, then nginx closed the connection after a send timeout only. *) Bugfix: the "[alert] zero size buf" error when FastCGI server was used. *) Bugfixes in the "limit_zone" directive.
author Igor Sysoev <http://sysoev.ru>
date Fri, 19 Jan 2007 00:00:00 +0300
parents 052a7b1d40e5
children 704622b2528a
comparison
equal deleted inserted replaced
275:1779577cb845 276:c5c2b2883984
1
2 Changes with nginx 0.5.8 19 Jan 2007
3
4 *) Bugfix: a segmentation fault might occur if
5 "client_body_in_file_only on" was used and a request body was small.
6
7 *) Bugfix: a segmentation fault occurred if
8 "client_body_in_file_only on" and "proxy_pass_request_body off" or
9 "fastcgi_pass_request_body off" directives were used, and nginx
10 switched to a next upstream.
11
12 *) Bugfix: if the "proxy_buffering off" directive was used and a client
13 connection was non-active, then the connection was closed after send
14 timeout; bug appeared in 0.4.7.
15
16 *) Bugfix: if the "epoll" method was used and a client closed a
17 connection prematurely, then nginx closed the connection after a
18 send timeout only.
19
20 *) Bugfix: the "[alert] zero size buf" error when FastCGI server was
21 used.
22
23 *) Bugfixes in the "limit_zone" directive.
24
1 25
2 Changes with nginx 0.5.7 15 Jan 2007 26 Changes with nginx 0.5.7 15 Jan 2007
3 27
4 *) Feature: the ssl_session_cache storage optimization. 28 *) Feature: the ssl_session_cache storage optimization.
5 29
77 $r->log_error, and $r->sleep methods. 101 $r->log_error, and $r->sleep methods.
78 102
79 *) Feature: the $r->variable method supports variables that do not 103 *) Feature: the $r->variable method supports variables that do not
80 exist in nginx configuration. 104 exist in nginx configuration.
81 105
82 *) Bugfix: the $r->has_request_body method did work. 106 *) Bugfix: the $r->has_request_body method did not work.
83 107
84 108
85 Changes with nginx 0.5.2 11 Dec 2006 109 Changes with nginx 0.5.2 11 Dec 2006
86 110
87 *) Bugfix: if the "proxy_pass" directive used the name of the 111 *) Bugfix: if the "proxy_pass" directive used the name of the
461 485
462 *) Bugfix: the $r->headers_in("Cookie") of the ngx_http_perl_module now 486 *) Bugfix: the $r->headers_in("Cookie") of the ngx_http_perl_module now
463 returns all "Cookie" header lines. 487 returns all "Cookie" header lines.
464 488
465 *) Bugfix: a segmentation fault occurred if 489 *) Bugfix: a segmentation fault occurred if
466 "client_body_in_file_only on" was used and nginx was switches to a 490 "client_body_in_file_only on" was used and nginx switched to a next
467 next upstream. 491 upstream.
468 492
469 *) Bugfix: on some condition while reconfiguration character codes 493 *) Bugfix: on some condition while reconfiguration character codes
470 inside the "charset_map" may be treated invalid; bug appeared in 494 inside the "charset_map" may be treated invalid; bug appeared in
471 0.3.50. 495 0.3.50.
472 496