6d5d27
#############
6d5d27
Upgrade notes
6d5d27
#############
6d5d27
6d5d27
To resolve numerous security flaws, the nginx package was updated to 1.10.x.
6d5d27
6d5d27
You should review your configuration files in /etc/nginx to determine if there
6d5d27
are any incompatibilities. Below is a summary of the main incompatible changes.
6d5d27
Some nginx directives have been changed or removed, so you may need to modify
6d5d27
your configuration.
6d5d27
6d5d27
Please see upstream release notes for a complete list of new features,
6d5d27
bug fixes, and changes: http://nginx.org/en/CHANGES-1.10
6d5d27
One notable feature is support for HTTP/2.
6d5d27
6d5d27
Nginx gained support for dynamic modules. As part of this update, dynamic
6d5d27
modules have been split into subpackages. For the time being these are hard
6d5d27
dependencies to aid the upgrade path. When you install nginx, all of these
6d5d27
modules are installed and enabled by default:
6d5d27
  - nginx-mod-http-geoip
6d5d27
  - nginx-mod-http-image-filter
6d5d27
  - nginx-mod-http-perl
6d5d27
  - nginx-mod-http-xslt-filter
6d5d27
  - nginx-mod-mail
6d5d27
  - nginx-mod-stream
6d5d27
6d5d27
Changes with nginx 1.10.x
6d5d27
6d5d27
    *) Change: non-idempotent requests (POST, LOCK, PATCH) are no longer
6d5d27
       passed to the next server by default if a request has been sent to a
6d5d27
       backend; the "non_idempotent" parameter of the "proxy_next_upstream"
6d5d27
       directive explicitly allows retrying such requests.
6d5d27
6d5d27
    *) Change: now the "output_buffers" directive uses two buffers by
6d5d27
       default.
6d5d27
6d5d27
    *) Change: now nginx limits subrequests recursion, not simultaneous
6d5d27
       subrequests.
6d5d27
6d5d27
    *) Change: now nginx checks the whole cache key when returning a
6d5d27
       response from cache.
6d5d27
       Thanks to Gena Makhomed and Sergey Brester.
6d5d27
6d5d27
    *) Change: the "proxy_downstream_buffer" and "proxy_upstream_buffer"
6d5d27
       directives of the stream module are replaced with the
6d5d27
       "proxy_buffer_size" directive.
6d5d27
6d5d27
    *) Change: duplicate "http", "mail", and "stream" blocks are now
6d5d27
       disallowed.
6d5d27
6d5d27
    *) Change: now SSLv3 protocol is disabled by default.
6d5d27
6d5d27
    *) Change: some long deprecated directives are not supported anymore.
6d5d27
6d5d27
    *) Change: obsolete aio and rtsig event methods have been removed.
6d5d27
6d5d27
Changes with nginx 1.8.x
6d5d27
6d5d27
    *) Change: the "sendfile" parameter of the "aio" directive is
6d5d27
       deprecated; now nginx automatically uses AIO to pre-load data for
6d5d27
       sendfile if both "aio" and "sendfile" directives are used.
6d5d27
6d5d27
    *) Change: now the "If-Modified-Since", "If-Range", etc. client request
6d5d27
       header lines are passed to a backend while caching if nginx knows in
6d5d27
       advance that the response will not be cached (e.g., when using
6d5d27
       proxy_cache_min_uses).
6d5d27
6d5d27
    *) Change: now after proxy_cache_lock_timeout nginx sends a request to a
6d5d27
       backend with caching disabled; the new directives
6d5d27
       "proxy_cache_lock_age", "fastcgi_cache_lock_age",
6d5d27
       "scgi_cache_lock_age", and "uwsgi_cache_lock_age" specify a time
6d5d27
       after which the lock will be released and another attempt to cache a
6d5d27
       response will be made.
6d5d27
6d5d27
    *) Change: the "log_format" directive can now be used only at http
6d5d27
       level.
6d5d27
6d5d27
    *) Change: now nginx takes into account the "Vary" header line in a
6d5d27
       backend response while caching.
6d5d27
6d5d27
    *) Change: the deprecated "limit_zone" directive is not supported
6d5d27
       anymore.
6d5d27
6d5d27
    *) Change: now the "stub_status" directive does not require a parameter.
6d5d27
6d5d27
    *) Change: URI escaping now uses uppercase hexadecimal digits.
6d5d27
       Thanks to Piotr Sikora.
6d5d27