Ok,
What about the other way around. Is it possible to disable http2 for one
server block, via config or via code?
Other than that, what are the alternatives? One listen on one IP for http2
and on another for http1?
Thanks!
On Thu, Jun 23, 2016 at 7:06 AM, itpp2012
wrote:
> Valentin V. Barten
Valentin V. Bartenev Wrote:
> What effect do you expect? Since clients are able to request
> different hosts
> using single HTTP/2 connection, closing the connection in one server
> block
> will break everything.
I'm just venting an (untested) idea, some other way to tell the client to
revert b
On Thursday 23 June 2016 04:35:45 itpp2012 wrote:
> Valentin V. Bartenev Wrote:
> ---
> > > Is it possible to enable http2 in only one of several name-based
> > servers?
> > >
> > [..]
> >
> > No, it's not possible.
>
> Would it be a big (api)
Valentin V. Bartenev Wrote:
---
> > Is it possible to enable http2 in only one of several name-based
> servers?
> >
> [..]
>
> No, it's not possible.
Would it be a big (api) change to add a server block session flag?
ngx_http_v2_init(ngx_event
On Wednesday 22 June 2016 18:32:47 Marcelo MD wrote:
> Hi,
>
> Is it possible to enable http2 in only one of several name-based servers?
>
[..]
No, it's not possible.
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.n
Hi,
Is it possible to enable http2 in only one of several name-based servers?
I have the following scenario:
server {
listen 443 ssl;
server_name www.example.com;
ssl_certificate www.example.com.crt;
...
}
server {
listen 443 ssl http2;
server_name
