Re:Tools for debugging, testing and using HTTP/2
by ghedo on Sunday December 06, 2015 @05:07PM
(#10686879)
Using curl is one way:
% curl -v https://google.com/ --http2
* Trying 2607:f8b0:4007:802::1008...
* Connected to google.com (2607:f8b0:4007:802::1008) port 443 (#0)
* found 180 certificates in /etc/ssl/certs/ca-certificates.crt
* found 722 certificates in /etc/ssl/certs
* ALPN, offering h2
* ALPN, offering http/1.1
* SSL connection using TLS1.2 / ECDHE_ECDSA_AES_128_GCM_SHA256
...
* ALPN, server accepted to use h2
The above is with the GnuTLS build on Debian, recent enough OpenSSL versions support both NPN and ALPN.
Re:Tools for debugging, testing and using HTTP/2
by achillean on Monday December 07, 2015 @01:28AM
(#10688199)
Shodan also keeps track of the ALPN negotation results, see the "Negotiated HTTP Versions" chart: https://www.shodan.io/report/tbi6kDZa
Re:Tools for debugging, testing and using HTTP/2
by Ambroos on Monday December 07, 2015 @06:11AM
(#10688735)
Next protocols supported are strictly NPN only. If you want to check ALPN support for a specific connection type you can use the following command:
openssl s_client -alpn h2 -connect news.ycombinator.com:443
Near the end of the output you'll see the ALPN protocol or `No ALPN negotiated`. I haven't managed to get a list of server-supported protocols so far, not sure if that's even possible with ALPN.This is with LibreSSL 2.3, but I expect OpenSSL 1.0.2 to support it too.
This is one of those details that I believe are the real roadblocks to HTTP/2.0 support. Google is trying to drive adoption by deprecating old features like NPN from Chrome, but people setting their servers up with HTTP/2.0 don't even know about these details or how it affects them.