[nginx] support http2 per server

[Neil Craig]

WRT the below, he H2 RFC includes a new status code to deal with thus, 421:
https://tools.ietf.org/html/rfc7540#section-9.1.2

Client support is poor right no so it'd be good if sending 421 was optional perhaps.

Cheers

Sent from my iPhone

On 8 Jun 2017, at 18:17, 洪志道 <hongzhidao at gmail.com<mailto:hongzhidao at gmail.com>> wrote:

Thanks.

On Fri, Jun 9, 2017 at 1:09 AM, Valentin V. Bartenev <vbart at nginx.com<mailto:vbart at nginx.com>> wrote:
On Friday 09 June 2017 00:08:06 洪志道 wrote:
> "
>
>    For "https" resources, connection reuse additionally depends on
>    having a certificate that is valid for the host in the URI.  The
>    certificate presented by the server MUST satisfy any checks that the
>    client would perform when forming a new TLS connection for the host
>    in the URI.
>
> "
>
>
> It seems the brower can prevent the unreasonable behavior.
>
>
> In reallity, It still exist some clients that dosen't perfom well in http2.
>
> So it's kind of valuable to enable http2 by server.
>
>
> It's not a good idea the put the patch in nginx,
>
> Can you help to check the patch whether contains serious problem?
>
>
> Maybe it's helpful for other guys.
>
>
> Thanks again.
>
[..]

The most serious problem with the patch, that it gives an illusion
that HTTP/2 can be enabled per virtual server basis, but in fact it
doesn't prevent requests to any server on particular listen socket
using already existing HTTP/2 connection.

Also please note that with your patch clients are still able to
negotiate HTTP/2 even if nginx doesn't announce it.

I don't see any other serious problems.

  wbr, Valentin V. Bartenev

_______________________________________________
nginx-devel mailing list
nginx-devel at nginx.org<mailto:nginx-devel at nginx.org>
http://mailman.nginx.org/mailman/listinfo/nginx-devel

_______________________________________________
nginx-devel mailing list
nginx-devel at nginx.org<mailto:nginx-devel at nginx.org>
http://mailman.nginx.org/mailman/listinfo/nginx-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx-devel/attachments/20170608/8a02b362/attachment.html>