Nginx-1.11.0

Changes with nginx 1.11.0 24 May
2016

*) Feature: the "transparent" parameter of the "proxy_bind",
   "fastcgi_bind", "memcached_bind", "scgi_bind", and "uwsgi_bind"
   directives.

*) Feature: the $request_id variable.

*) Feature: the "map" directive supports combinations of multiple
   variables as resulting values.

*) Feature: now nginx checks if EPOLLRDHUP events are supported by
   kernel, and optimizes connection handling accordingly if the 

“epoll”
method is used.

*) Feature: the "ssl_certificate" and "ssl_certificate_key" 

directives
can be specified multiple times to load certificates of different
types (for example, RSA and ECDSA).

*) Feature: the "ssl_ecdh_curve" directive now allows specifying a 

list
of curves when using OpenSSL 1.0.2 or newer; by default a list
built
into OpenSSL is used.

*) Change: to use DHE ciphers it is now required to specify 

parameters
using the “ssl_dhparam” directive.

*) Feature: the $proxy_protocol_port variable.

*) Feature: the $realip_remote_port variable in the
   ngx_http_realip_module.

*) Feature: the ngx_http_realip_module is now able to set the client
   port in addition to the address.

*) Change: the "421 Misdirected Request" response now used when
   rejecting requests to a virtual server different from one 

negotiated
during an SSL handshake; this improves interoperability with some
HTTP/2 clients when using client certificates.

*) Change: HTTP/2 clients can now start sending request body
   immediately; the "http2_body_preread_size" directive controls 

size of
the buffer used before nginx will start reading client request
body.

*) Bugfix: cached error responses were not updated when using the
   "proxy_cache_bypass" directive.


Maxim D.
http://nginx.org/

nice RSA + ECDSA certs support !

what’s the recommended way to setup HTTP Public Key Pinning with regards
to
dual SSL certificates ?

Posted at Nginx Forum:

*) Feature: the "map" directive supports combinations of multiple
   variables as resulting values.

Does this mean this ticket can be resolved?
https://trac.nginx.org/nginx/ticket/663

On Wed, May 25, 2016 at 12:19 AM, George [email protected]

On 25.05.2016 12:01, Alexey Genus wrote:

*) Feature: the "map" directive supports combinations of multiple
    variables as resulting values.

Does this mean this ticket can be resolved?
#663 (Variable interpolation inside Map directive) – nginx

Yes, it is resolved.