Have a Cookie? :)

Our site uses cookies to provide functionality and performance as well as for social media and advertising purposes. Social media and advertising cookies of third parties are used to offer you social media functionalities and personalized ads for NGINX content and offers. To get more information about these cookies and how we process personal data, check our Privacy Policy. Do you accept the use of cookies and the processing of personal data involved?

Your Cookie Settings

Site functionality and performance

These cookies are required for NGINX site functionality and are therefore always enabled. These include cookies that allow you to be remembered as you explore the NGINX site, help make the shopping cart and checkout process possible as well as assist in security issues and conforming to regulations. To use the NGINX website, you have to consent to these cookies and the processing of personal data according to the NGINX website terms of use and privacy policy.

Social media and advertising

Social media cookies offer the possibility to connect you to your social networks and share content from our website through social media. Advertising cookies (of third parties) collect information to help better tailor NGINX advertising to your interests, both within and beyond NGINX websites. De-selecting these cookies may result in seeing advertising that is not as relevant to you or you not being able to link effectively with Facebook, Twitter, or other social networks and/or not allowing you to share content on social media.

Length of Vary and ETag cache headers increased to 128 bytes; note that the on‑disk cache format has changed, so cached content is invalidated after the upgrade and must be refreshed from the origin server

mandatory parameter to the health_check directive (HTTP and Stream) which requires servers newly added to an upstream group to pass the associated health check before receiving real traffic

Cache manager support for iterative operations mode when deleting old cache files, reducing the disk load (see the manager_files, manager_threshold, and manager_sleep parameters of the proxy_cache_path directive)

Note: NGINX Plus R10 is the last release to include the nginx-plus-extras package. Any subscribers using this package should migrate to the nginx-plus package and then install the needed dynamic modules.

Support for retrieving upstream servers configuration via DNS SRV records, configured with the new service parameter to the server directive

Automatic retrying of DNS requests over TCP when UDP responses are truncated

Failed nonidempotent HTTP requests (POST, LOCK, PATCH) are no longer retried with the other servers in the upstream group, unless the non_idempotent parameter is included in the proxy_next_upstream directive

Improved cache metadata accounting

Automatic binding of worker processes to available CPUs using the the new auto parameter of the worker_cpu_affinity directive

Optional offloading of some cache write operations to thread pools, configured with the aio_writeon directive

Support for customizing the Server response header, as well as the signature in standard error messages

NGINX Plus R9 Updates

These are bug‑fix releases for NGINX Plus R9.

NGINX Plus R9 P125 May 2016

Fixed potential segmentation fault when writing a client request body to a temporary file. A specially crafted request may cause an NGINX worker process to crash due to a NULL pointer dereference (CVE-2016-4450).

Resolver: Limit CNAME resolutions to prevent remote attackers from causing a denial of service (CVE-2016-0747)

NGINX Plus Release 7 (R7)

NGINX open source build 1.9.4, 15 September 2015

NGINX Plus R7 is a feature release:

Support for HTTP/2 in the new nginx-plus-http2 package (the nginx-plus and nginx-plus-extras packages continue to support SPDY)

Note: Before installing the nginx-plus-http2 package, you must remove the spdy parameter on all listen directives in your configuration (replace it with the http2 and ssl parameters to enable support for HTTP/2). NGINX Plus fails to start if any listen directives have the spdy parameter.

NGINX Plus Release 5 (R5)

Sticky session timeout now applies from the most recent request in the session

Upstream “draining” can be used to remove an upstream server without interrupting any user sessions (new drain parameter to the upstream_conf directive)

Improved control over request retries in the event of failure, based on number of tries and time; also available for FastCGI, memcached, SCGI, and uwsgi modules

Vary field in response header is correctly handled for caching (multiple variants of the same resource can be cached); note that the on‑disk cache format has changed, so upgrading to R5 invalidates cached content