Re:An nginx.conf for 2017: HTTP/2, IPV6, HTML5 SSE, load bal...
by lstamour on Monday February 13, 2017 @05:53PM
(#13639585)
For Debian 8 (Jessie): There's a newer build of Nginx in jessie-backports with static OpenSSL 1.0.2: http://serverfault.com/questions/775298/debian-jessie-nginx-...
Re:An nginx.conf for 2017: HTTP/2, IPV6, HTML5 SSE, load bal...
by nailer on Monday February 13, 2017 @08:14PM
(#13640408)
Interesting. What's the maintenance policy for jessie-backports? If it's best-effort it might be better to avoid suggesting people use it for a package as frequently updated as openssl.
Re:An nginx.conf for 2017: HTTP/2, IPV6, HTML5 SSE, load bal...
by lstamour on Wednesday February 15, 2017 @03:48AM
(#13650635)
It is indeed best-effort. You can follow along on packaging in https://packages.qa.debian.org/n/nginx.html and https://packages.qa.debian.org/o/openssl.html as well as backports' security mailing lists.
Given what I'm seeing on the Nginx build currently in backports, I might rely on backports for dependencies, but I'd seriously consider building your own Nginx from source and/or pay attention yourself to security warnings.
Re:An nginx.conf for 2017: HTTP/2, IPV6, HTML5 SSE, load bal...
by scottlinux on Monday February 13, 2017 @06:17PM
(#13639778)
Debian 8 supports http/2 with the updated nginx provided in jessie-backports.
Biggest discovery when researching this was due to the ALPN requirement in Chrome [1], openssl 1.02 being required for ALPN, and the vagaries of Linux distro release schedules, Ubuntu 16.04 is the only LTS distro than can serve HTTP/2 to Chrome users.
When they're eventually announced, RHEL/CentOS 8 (Fedora already has the necessary openssl) and Debian 9 will also work. But right now Ubuntu is your only bet unless you want to build and maintain your own openssl. Which you don't.
[1] https://bugs.chromium.org/p/chromium/issues/detail?id=527066