It sounds right.
According to the same situation, how does http2 protocol force other
virtual servers to process certificate (ssl handshake).
Example:
server {
listen 443 http2;
a.com;
ssl_certi....;
}
server {
listen 443 http2;
b.com;
ssl_certi....;
}
We assume sni is 'a.com', then the connection contains different requests
with different domains.
That b.com will escape from ssl handshake. In fact, we need it to do the
ssl handshake.
Thanks.
On Thu, Jun 8, 2017 at 10:17 PM, Valentin V. Bartenev <vb...@nginx.com>
wrote:
> On Thursday 08 June 2017 12:07:29 洪志道 wrote:
> > Hi!
> > Now, http2 is enabled globally for 'listen' directive with ip:port.
> > It seems it's possible to enable by server with sni, alpn, npn.
> > Take a look, please.
> >
> [..]
>
> How will "sni, alpn, npn" prevent browser from asking other virtual
> servers using already opened HTTP/2 connection?
>
> wbr, Valentin V. Bartenev
>
> _______________________________________________
> nginx-devel mailing list
> nginx-devel@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx-devel
_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel
