On 2/6/16 1:00 PM, Валентин Бартенев wrote:
[snip]
So if I write:
listen 443 ssl http2;
in a server directive anywhere as dosumneted in
http://nginx.org/en/docs/http/ngx_http_v2_module.html#example, then
http2 is enabled in all servers on all IP's even if it's not
specifically enabled in a li
This patches are pretty stable (except you can't use different OCSP
responders for SHA1 and SHA256 certs and use different ssl_stapling_files).
https://github.com/wikimedia/operations-software-nginx/tree/wmf-1.9.3-1/debian/patches
On Fri, Feb 5, 2016 at 11:17 PM, Jon Emord wrote:
> Hello,
>
>
On Saturday 06 February 2016 12:44:08 Jim Ohlstein wrote:
> On 2/6/16 12:22 PM, Валентин Бартенев wrote:
> > On Saturday 06 February 2016 12:13:52 Jim Ohlstein wrote:
> >> Hello,
> >>
> >> I am running a WordPress multisite install and recently turned off http2
> >> on the domain in order to use a
On 2/6/16 12:22 PM, Валентин Бартенев wrote:
On Saturday 06 February 2016 12:13:52 Jim Ohlstein wrote:
Hello,
I am running a WordPress multisite install and recently turned off http2
on the domain in order to use a third party module which evidently
doesn't play nicely with http2 (echo module).
On Saturday 06 February 2016 12:13:52 Jim Ohlstein wrote:
> Hello,
>
> I am running a WordPress multisite install and recently turned off http2
> on the domain in order to use a third party module which evidently
> doesn't play nicely with http2 (echo module). In testing I noticed that
> the site
Hello,
I am running a WordPress multisite install and recently turned off http2
on the domain in order to use a third party module which evidently
doesn't play nicely with http2 (echo module). In testing I noticed that
the site was still being served with http2 enabled according to both
Chrom
