Upgrade to 1.11.0

Asked by Giovanni on 2016-05-31

Can you please upgrade the package to 1.11.0? This will solve the problem with http2 and "ssl_verify_client optional" used with different subdomains, as you can see in the changelog:

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.

If this isn't possible in the mainstream, I suggest you add a backport package.
Thanks again for your help.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu nginx Edit question
Assignee:
Thomas Ward Edit question
Solved by:
Giovanni
Solved:
2016-05-31
Last query:
2016-05-31
Last reply:
2016-05-31

What is the output of:

lsb_release -a; uname -a; apt-cache policy nginx

Thanks

Giovanni (gcrisci) said : #2

Here it is. Thanks for your help

Distributor ID: Ubuntu
Description: Ubuntu 16.04 LTS
Release: 16.04
Codename: xenial
Linux virtual-------- 4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:46 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
nginx:
  Installed: 1.10.0-0ubuntu0.16.04.1
  Candidate: 1.10.0-0ubuntu0.16.04.1
  Version table:
 *** 1.10.0-0ubuntu0.16.04.1 500
        500 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 Packages
        500 http://mirrors.digitalocean.com/ubuntu xenial-updates/main i386 Packages
        100 /var/lib/dpkg/status
     1.9.15-0ubuntu1 500
        500 http://mirrors.digitalocean.com/ubuntu xenial/main amd64 Packages
        500 http://mirrors.digitalocean.com/ubuntu xenial/main i386 Packages

Thomas Ward (teward) said : #3

Ubuntu will only be tracking Stable at this time, 1.10.x. If you need Mainline packages, the NGINX PPAs will be getting and update in the next day or so with the updated 1.11.x branch of NGINX.

Thomas Ward (teward) said : #4

The decision to track Stable and not Mainline was decided upon by the Server team during the Xenial development cycle; this was a decision that was decided through consensus and a lot of discussion within the Server team, and with other teams' input on the matter as well.

Giovanni (gcrisci) said : #5

You're right.
Since this bug is still present in the stable version, I will report it as a bug. It isn't necessary to upgrade to 1.11.0.
Thanks for your help