I think HTTP/2 should have opportunistic encryption support, as per https://lists.w3.org/Archives/Public/ietf-http-wg/2015JanMar/0106.html https://lists.w3.org/

I think HTTP/2 should have opportunistic encryption support, as per https://lists.w3.org/Archives/Public/ietf-http-wg/2015JanMar/0106.html https://lists.w3.org/Archives/Public/ietf-http-wg/2015JanMar.... As things stand, HTTP/2 is not done in compliance with RFC 7258 / BCP 188, because it doesn't do anything for the independent sites that cannot deploy the `https://` https://` address scheme for compatibility reasons. You basically either have to support the whole pre-1.2 TLS and forget about http:// http://, or you cannot have any TLS at all.