<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-2022-jp">
</head>
<body dir="auto">
<div>WRT the below, he H2 RFC includes a new status code to deal with thus, 421:</div>
<div id="AppleMailSignature"><a href="https://tools.ietf.org/html/rfc7540#section-9.1.2">https://tools.ietf.org/html/rfc7540#section-9.1.2</a></div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">Client support is poor right no so it'd be good if sending 421 was optional perhaps. </div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">Cheers<br>
<br>
Sent from my iPhone</div>
<div><br>
On 8 Jun 2017, at 18:17, 洪志道 <<a href="mailto:hongzhidao@gmail.com">hongzhidao@gmail.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div dir="ltr">Thanks.</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Jun 9, 2017 at 1:09 AM, 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 00:08:06 洪志道 wrote:<br>
> "<br>
><br>
> For "https" resources, connection reuse additionally depends on<br>
> having a certificate that is valid for the host in the URI. The<br>
> certificate presented by the server MUST satisfy any checks that the<br>
> client would perform when forming a new TLS connection for the host<br>
> in the URI.<br>
><br>
> "<br>
><br>
><br>
> It seems the brower can prevent the unreasonable behavior.<br>
><br>
><br>
> In reallity, It still exist some clients that dosen't perfom well in http2.<br>
><br>
> So it's kind of valuable to enable http2 by server.<br>
><br>
><br>
> It's not a good idea the put the patch in nginx,<br>
><br>
> Can you help to check the patch whether contains serious problem?<br>
><br>
><br>
> Maybe it's helpful for other guys.<br>
><br>
><br>
> Thanks again.<br>
><br>
</span>[..]<br>
<br>
The most serious problem with the patch, that it gives an illusion<br>
that HTTP/2 can be enabled per virtual server basis, but in fact it<br>
doesn't prevent requests to any server on particular listen socket<br>
using already existing HTTP/2 connection.<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>
I don't see any other serious problems.<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>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>nginx-devel mailing list</span><br>
<span><a href="mailto:nginx-devel@nginx.org">nginx-devel@nginx.org</a></span><br>
<span><a href="http://mailman.nginx.org/mailman/listinfo/nginx-devel">http://mailman.nginx.org/mailman/listinfo/nginx-devel</a></span></div>
</blockquote>
</body>
</html>