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