Am 12.03.2017 um 10:55 schrieb 彭勇:
i setup a ATS, then enable ssl and http2. curl shows ATS works fine. and chrome 56 shows it use protocal http 1.1 to connect to ATS. is there any ALPN / NPN negotiating problem between chrome and ATS? how can i serve http2 for chrome?
i doubt that you need anything to do, at least with ATS 7.0 curl don't need any param and choses HTTP2 automatically and so every browser can do - maybe your ATS is just outdated?
[harry@srv-rhsoft:~]$ curl --head https://www.thelounge.net/ HTTP/2.0 200 date:Sun, 12 Mar 2017 10:38:55 GMT x-dns-prefetch-control:off x-content-type-options:nosniff x-response-time:D=5111 us last-modified:Thu, 03 Sep 2015 09:04:29 GMT expires:Sun, 12 Mar 2017 12:38:55 GMT cache-control:public, proxy-revalidate etag:04ea5ea0c7b43fd2fb3ee18d68b96557 vary:Accept-Encoding,User-Agent content-type:text/html; charset=ISO-8859-1 age:6 content-length:11658
