<div dir="ltr">Get it, thanks.</div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jun 9, 2017 at 7:45 PM, Valentin V. Bartenev <span dir="ltr"><<a href="mailto:vbart@nginx.com" target="_blank">vbart@nginx.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Friday 09 June 2017 13:40:23 洪志道 wrote:<br>
> Hi, Valentin.<br>
><br>
> "<br>
> Also please note that with your patch clients are still able to<br>
> negotiate HTTP/2 even if nginx doesn't announce it.<br>
> "<br>
><br>
> Two points:<br>
> 1. The patch forbids the clients explicitly not support HTTP/2 doing v2 (<br>
> ngx_http_v2_init).<br>
>     How to follow you mean of "with the patch, clients are still able to<br>
> negotiate HTTP/2"<br>
> 2. "even if nginx doesn't announce it"<br>
>     Is it related to nginx?<br>
><br>
</span>[..]<br>
<br>
Your patch prevents advertising the protocol using ALPN and NPN, but<br>
selecting protocol happens here (this part of code isn't touched):<br>
<a href="http://hg.nginx.org/nginx/file/tip/src/http/ngx_http_request.c#l808" rel="noreferrer" target="_blank">http://hg.nginx.org/nginx/<wbr>file/tip/src/http/ngx_http_<wbr>request.c#l808</a><br>
<br>
In case of NPN, client can select protocol even if it hasn't been<br>
advertised by the server.<br>
<div class="HOEnZb"><div class="h5"><br>
  wbr, Valentin V. Bartenev<br>
<br>
______________________________<wbr>_________________<br>
nginx-devel mailing list<br>
<a href="mailto:nginx-devel@nginx.org">nginx-devel@nginx.org</a><br>
<a href="http://mailman.nginx.org/mailman/listinfo/nginx-devel" rel="noreferrer" target="_blank">http://mailman.nginx.org/<wbr>mailman/listinfo/nginx-devel</a></div></div></blockquote></div><br></div>