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