I’ve recently updated this blog and icanhazip.com to enable HTTP/2! This probably won’t have much of an effect on users who query icanhazip.com with automated tools, but it should deliver the content on this blog a little faster. If you’re using an older, non-HTTP/2 client — don’t worry. All of the sites will continue working for you as they always have.
Head on over to Wikipedia to learn more about HTTP/2 and its benefits.
Also, I’ve revised the list of allowed TLS ciphers so that stronger ciphers are required. If you’re having issues with a particular client, please let me know.
Works on icanhazip.com but not (yet) on major.io
My 2 cents ^^
# Most usefull tools for HTTP2 by cloudflare
https://blog.cloudflare.com/tools-for-debugging-testing-and-using-http-2/
# Quick HTTP2 troubleshotting command
openssl s_client -connect major.io:443 -nextprotoneg ” | grep Protocols
curl -I –http2 https://major.io
My browser still show http/1.1 (‘latest’ chrome on w10). Are you using a newer OpenSSL version that supports ALPN ?
Indeed, you may be right, from sslabs test
> ALPN Yes
> NPN Yes h2 http/1.1
Google Chrome only use ALPN now, see link below
link: https://ma.ttias.be/day-google-chrome-disables-http2-nearly-everyone-may-31st-2016/
$ curl -I icanhazip.com
HTTP/1.1 200 OK
$ curl -I –http2 http://icanhazip.com
curl: (1) Unsupported protocol
$curl -I –http2 https://major.io
curl: (1) Unsupported protocol
$ openssl s_client -connect major.io:443 -nextprotoneg ” | grep Protocols
140020489098896:error:140920E3:SSL routines:SSL3_GET_SERVER_HELLO:parse tlsext:s3_clnt.c:1074:
Protocols advertised by server: http/1.1
$ curl –version
curl 7.50.1 (x86_64-pc-msys) libcurl/7.50.1 OpenSSL/1.0.2h zlib/1.2.8 libidn/1.33 libssh2/1.7.0
Protocols: dict file ftp ftps gopher http https imap imaps pop3 pop3s rtsp scp sftp smb smbs smtp smtps telnet tftp
Features: Debug IDN IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB SSL libz TLS-SRP UnixSockets Metalink
Do I need a newer version of curl for this?