File nginx-1.2.changes of Package nginx-1.2 - j0ke.net Open Build Service

File nginx-1.2.changes of Package nginx-1.2 (Revision 6fd4517d7d58756f2038bf20dc104909)

Currently displaying revision 6fd4517d7d58756f2038bf20dc104909, show latest

-------------------------------------------------------------------
Thu Jul  5 14:33:04 UTC 2012 - cs@linux-administrator.com

- upstream update 1.2.2
  * Change: the "single" parameter of the "keepalive" directive is now
    ignored.
  * Change: SSL compression is now disabled when using all versions of
    OpenSSL, including ones prior to 1.0.0.
  * Feature: the "proxy_pass", "fastcgi_pass", "scgi_pass", "uwsgi_pass"
    directives, and the "server" directive inside the "upstream" block,
    now support IPv6 addresses.
  * Feature: the "resolver" directive now support IPv6 addresses and an
    optional port specification.
  * Feature: the "least_conn" directive inside the "upstream" block.
  * Feature: it is now possible to specify a weight for servers while
    using the "ip_hash" directive.
  * Feature: it is now possible to use the "ip_hash" directive to balance
    IPv6 clients.
  * Feature: the $status variable can now be used not only in the
    "log_format" directive.
  * Bugfix: nginx could not be built with ngx_cpp_test_module; the bug
    had appeared in 1.1.12.
  * Bugfix: access to variables from SSI and embedded perl module might
    not work after reconfiguration.
  * Bugfix: in the ngx_http_xslt_filter_module.
  * Bugfix: memory leak if $geoip_org variable was used.
  * Bugfix: in the "proxy_cookie_domain" and "proxy_cookie_path"
    directives.
  * Bugfix: a segmentation fault might occur in a worker process on
    shutdown if the "resolver" directive was used.
  * Bugfix: a segmentation fault might occur in a worker process if the
    ngx_http_mp4_module was used.
  * Bugfix: in the ngx_http_mp4_module.
  * Bugfix: a segmentation fault might occur in a worker process if
    conflicting wildcard server names were used.
  * Bugfix: nginx might be terminated abnormally on a SIGBUS signal on
    ARM platform.
  * Bugfix: an alert "sendmsg() failed (9: Bad file number)" on HP-UX
    while reconfiguration.

-------------------------------------------------------------------
Sun Jun 17 10:40:51 UTC 2012 - cs@linux-administrator.com

- upstream update 1.2.1
  * Security: now nginx/Windows ignores trailing dot in URI path
    component, and does not allow URIs with ":$" in it.
  * 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.
  * Bugfix: in the ngx_http_fastcgi_module.

-------------------------------------------------------------------
Sun May  6 07:42:07 UTC 2012 - cs@linux-administrator.com

- upstream update 1.2.0
  * Bugfix: a segmentation fault might occur in a worker process if the
    "try_files" directive was used; the bug had appeared in 1.1.19.
  * Bugfix: response might be truncated if there were more than IOV_MAX
    buffers used.
  * Bugfix: in the "crop" parameter of the "image_filter" directive.