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 <[email protected]> wrote: > 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 back to pre-http2 connections when hitting a server block, maybe a > simple return would be enough. > > connect site.ru (h2) > connect.h2 site2.ru (deny h2, client should revert to http(s)) > > Posted at Nginx Forum: > https://forum.nginx.org/read.php?2,267795,267808#msg-267808 > > _______________________________________________ > nginx mailing list > [email protected] > http://mailman.nginx.org/mailman/listinfo/nginx > -- Marcelo Mallmann Dias
_______________________________________________ nginx mailing list [email protected] http://mailman.nginx.org/mailman/listinfo/nginx
