comparison CHANGES @ 260:0effe91f6083 NGINX_0_5_0

nginx 0.5.0 *) Change: the parameters in the "%name" form in the "log_format" directive are not supported anymore. *) Change: the "proxy_upstream_max_fails", "proxy_upstream_fail_timeout", "fastcgi_upstream_max_fails", "fastcgi_upstream_fail_timeout", "memcached_upstream_max_fails", and "memcached_upstream_fail_timeout" directives are not supported anymore. *) Feature: the "server" directive in the "upstream" context supports the "max_fails", "fail_timeout", and "down" parameters. *) Feature: the "ip_hash" directive inside the "upstream" block. *) Feature: the WAIT status in the "Auth-Status" header line of the IMAP/POP3 proxy authentication server response. *) Bugfix: nginx could not be built on 64-bit platforms; bug appeared in 0.4.14.
author Igor Sysoev <http://sysoev.ru>
date Mon, 04 Dec 2006 00:00:00 +0300
parents 6ae1357b7b7c
children e0b1d0a6c629
comparison
equal deleted inserted replaced
259:c68f18041059 260:0effe91f6083
1
2 Changes with nginx 0.5.0 04 Dec 2006
3
4 *) Change: the parameters in the "%name" form in the "log_format"
5 directive are not supported anymore.
6
7 *) Change: the "proxy_upstream_max_fails",
8 "proxy_upstream_fail_timeout", "fastcgi_upstream_max_fails",
9 "fastcgi_upstream_fail_timeout", "memcached_upstream_max_fails", and
10 "memcached_upstream_fail_timeout" directives are not supported
11 anymore.
12
13 *) Feature: the "server" directive in the "upstream" context supports
14 the "max_fails", "fail_timeout", and "down" parameters.
15
16 *) Feature: the "ip_hash" directive inside the "upstream" block.
17
18 *) Feature: the WAIT status in the "Auth-Status" header line of the
19 IMAP/POP3 proxy authentication server response.
20
21 *) Bugfix: nginx could not be built on 64-bit platforms; bug appeared
22 in 0.4.14.
23
1 24
2 Changes with nginx 0.4.14 27 Nov 2006 25 Changes with nginx 0.4.14 27 Nov 2006
3 26
4 *) Feature: the "proxy_pass_error_message" directive in IMAP/POP3 proxy. 27 *) Feature: the "proxy_pass_error_message" directive in IMAP/POP3 proxy.
5 28
6 *) Bugfix: ngx_http_perl_module did nto work with perl built with the 29 *) Feature: now configure detects system PCRE library on FreeBSD,
30 Linux, and NetBSD.
31
32 *) Bugfix: ngx_http_perl_module did not work with perl built with the
7 threads support; bug appeared in 0.3.38. 33 threads support; bug appeared in 0.3.38.
8 34
9 *) Bugfix: !!!!!!!!!! segfault perl. 35 *) Bugfix: ngx_http_perl_module did not work if perl was called
10 36 recursively.
11 *) Bugfix: !!!!!!!!!! recursive perl.
12 37
13 *) Bugfix: nginx ignored a host name in an request line. 38 *) Bugfix: nginx ignored a host name in an request line.
14 39
15 *) Bugfix: !!!!!!!!!! endless loop when too many FastCGI sent too many 40 *) Bugfix: a worker process may got caught in an endless loop, if a
16 to stderr 41 FastCGI server sent too many data to the stderr.
17 42
18 *) Bugfix: !!!!!!!! negative upstream response time 43 *) Bugfix: the $upstream_response_time variable may be negative if the
44 system time was changed backward.
19 45
20 *) Bugfix: the "Auth-Login-Attempt" parameter was not sent to IMAP/POP3 46 *) Bugfix: the "Auth-Login-Attempt" parameter was not sent to IMAP/POP3
21 proxy authentication server when POP3 was used. 47 proxy authentication server when POP3 was used.
22 48
23 *) Bugfix: a segmentation fault might occur if connect to IMAP/POP3 49 *) Bugfix: a segmentation fault might occur if connect to IMAP/POP3
351 Changes with nginx 0.3.53 07 Jul 2006 377 Changes with nginx 0.3.53 07 Jul 2006
352 378
353 *) Change: the "add_header" directive adds the string to 204, 301, and 379 *) Change: the "add_header" directive adds the string to 204, 301, and
354 302 responses. 380 302 responses.
355 381
356 *) Feature: the "server" directive if the "upstream" context supports 382 *) Feature: the "server" directive in the "upstream" context supports
357 the "weight" parameter. 383 the "weight" parameter.
358 384
359 *) Feature: the "server_name" directive supports the "*" wildcard. 385 *) Feature: the "server_name" directive supports the "*" wildcard.
360 386
361 *) Feature: nginx supports the request body size more than 2G. 387 *) Feature: nginx supports the request body size more than 2G.