A equipe de desenvolvimento do nginx, servidor web e de proxy reverso de código fonte aberto, disponibilizou uma versão de desenvolvimento (1.3.1) contendo 7 correções e 4 novas funcionalidades e uma versão estável (1.2.1) com 9 Correções e 4 novas funcionalidades
Mudanças no nginx 1.3.1
- Funcionalidade: the "proxy_pass", "fastcgi_pass", "scgi_pass", "uwsgi_pass" directives, and the "server" directive inside the "upstream" block, now support IPv6 addresses.
- Funcionalidade: the "resolver" directive now support IPv6 addresses and an optional port specification.
- Funcionalidade: the "least_conn" directive inside the "upstream" block.
- Funcionalidade: it is now possible to specify a weight for servers while using the "ip_hash" directive.
- Correção: a segmentation fault might occur in a worker process if the "image_filter" directive was used; the bug had appeared in 1.3.0.
- Correção: nginx could not be built with ngx_cpp_test_module; the bug had appeared in 1.1.12.
- Correção: access to variables from SSI and embedded perl module might not work after reconfiguration.
- Correção: in the ngx_http_xslt_filter_module.
- Correção: memory leak if $geoip_org variable was used.
- Correção: in the "proxy_cookie_domain" and "proxy_cookie_path" directives.
- Correção: now nginx/Windows ignores trailing dot in URI path component, and does not allow URIs with ":$" in it.
Mudanças no nginx 1.2.1
- Funcionalidade: the "debug_connection" directive now supports IPv6 addresses and the "unix:" parameter.
- Funcionalidade: the "set_real_ip_from" directive and the "proxy" parameter of the "geo" directive now support IPv6 addresses.
- Funcionalidade: the "real_ip_recursive", "geoip_proxy", and "geoip_proxy_recursive" directives.
- Funcionalidade: the "proxy_recursive" parameter of the "geo" directive.
- Correção: a segmentation fault might occur in a worker process if the "resolver" directive was used.
- Correção: 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.
- Correção: a segmentation fault might occur in a worker process if the "rewrite" directive was used and new request arguments in a replacement used variables.
- Correção: nginx might hog CPU if the open file resource limit was reached.
- Correção: 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.
- Correção: adding the "down" parameter of the "server" directive might cause unneeded client redistribution among backend servers if the "ip_hash" directive was used.
- Correção: socket leak.
- Correção: in the ngx_http_fastcgi_module.
-
Correção: now nginx/Windows ignores trailing dot in URI path component, and does not allow URIs with ":$" in it.