comparison CHANGES @ 674:4dcaf40cc702 NGINX_1_3_0

nginx 1.3.0 *) Feature: the "debug_connection" directive now supports IPv6 addresses and the "unix:" parameter. *) Feature: the "set_real_ip_from" directive and the "proxy" parameter of the "geo" directive now support IPv6 addresses. *) Feature: the "real_ip_recursive", "geoip_proxy", and "geoip_proxy_recursive" directives. *) Feature: the "proxy_recursive" parameter of the "geo" directive. *) Bugfix: a segmentation fault might occur in a worker process if the "resolver" directive was used. *) Bugfix: a segmentation fault might occur in a worker process if the "fastcgi_pass", "scgi_pass", or "uwsgi_pass" directives were used and backend returned incorrect response. *) Bugfix: a segmentation fault might occur in a worker process if the "rewrite" directive was used and new request arguments in a replacement used variables. *) Bugfix: nginx might hog CPU if the open file resource limit was reached. *) Bugfix: nginx might loop infinitely over backends if the "proxy_next_upstream" directive with the "http_404" parameter was used and there were backup servers specified in an upstream block. *) Bugfix: adding the "down" parameter of the "server" directive might cause unneeded client redistribution among backend servers if the "ip_hash" directive was used. *) Bugfix: socket leak. Thanks to Yichun Zhang. *) Bugfix: in the ngx_http_fastcgi_module.
author Igor Sysoev <http://sysoev.ru>
date Tue, 15 May 2012 00:00:00 +0400
parents f41d4b305d22
children bfa81a0490a2
comparison
equal deleted inserted replaced
673:1e5c7a976f48 674:4dcaf40cc702
1
2 Changes with nginx 1.3.0 15 May 2012
3
4 *) Feature: the "debug_connection" directive now supports IPv6 addresses
5 and the "unix:" parameter.
6
7 *) Feature: the "set_real_ip_from" directive and the "proxy" parameter
8 of the "geo" directive now support IPv6 addresses.
9
10 *) Feature: the "real_ip_recursive", "geoip_proxy", and
11 "geoip_proxy_recursive" directives.
12
13 *) Feature: the "proxy_recursive" parameter of the "geo" directive.
14
15 *) Bugfix: a segmentation fault might occur in a worker process if the
16 "resolver" directive was used.
17
18 *) Bugfix: a segmentation fault might occur in a worker process if the
19 "fastcgi_pass", "scgi_pass", or "uwsgi_pass" directives were used and
20 backend returned incorrect response.
21
22 *) Bugfix: a segmentation fault might occur in a worker process if the
23 "rewrite" directive was used and new request arguments in a
24 replacement used variables.
25
26 *) Bugfix: nginx might hog CPU if the open file resource limit was
27 reached.
28
29 *) Bugfix: nginx might loop infinitely over backends if the
30 "proxy_next_upstream" directive with the "http_404" parameter was
31 used and there were backup servers specified in an upstream block.
32
33 *) Bugfix: adding the "down" parameter of the "server" directive might
34 cause unneeded client redistribution among backend servers if the
35 "ip_hash" directive was used.
36
37 *) Bugfix: socket leak.
38 Thanks to Yichun Zhang.
39
40 *) Bugfix: in the ngx_http_fastcgi_module.
41
1 42
2 Changes with nginx 1.2.0 23 Apr 2012 43 Changes with nginx 1.2.0 23 Apr 2012
3 44
4 *) Bugfix: a segmentation fault might occur in a worker process if the 45 *) Bugfix: a segmentation fault might occur in a worker process if the
5 "try_files" directive was used; the bug had appeared in 1.1.19. 46 "try_files" directive was used; the bug had appeared in 1.1.19.