4 ms·
Leaving the specific letters aside, I wonder about this comment in https://github.com/http2/http2-spec/issues/101 https://github.com/http2/http2-spec/issues/101
by JoshTriplett 11y ago
Leaving the specific letters aside, I wonder about this comment in https://github.com/http2/http2-spec/issues/101 https://github.com/http2/http2-spec/issues/101:
"And the experimental data we have (what there is of it) suggests that we need to make this look like an unknown HTTP/1.1 method (or two)."
Anyone know what experimental data this refers to, and why this helps? This gets encapsulated inside TLS; nothing should know about it except the endpoints, both of which need to understand HTTP/2.
- cesarb 11y agoHTTP/2 is not TLS-only, even though major browsers will only use it over TLS. And even when over TLS, the TLS connection might terminate in a separate machine, it going cleartext the rest of the way.
- JoshTriplett 11y ago> HTTP/2 is not TLS-only, even though major browsers will only use it over TLS. Which in practice will (hopefully) make it TLS-only. As I recall, one of the original motivations to require TLS, and one of the reasons browsers plan to mandate TLS (apart from the obvious), was specifically to avoid broken "transparent" proxies. > And even when over TLS, the TLS connection might terminate in a separate machine, it going cleartext the rest of the way. If the server uses a TLS frontend device and passes cleartext to a backend, then apart from that being a really bad idea from a security perspective, they should know better than to allow that to pass through a broken transparent proxy.
- mnot 11y agoSee: https://lists.w3.org/Archives/Public/ietf-http-wg/2013JanMar/0910.html https://lists.w3.org/Archives/Public/ietf-http-wg/2013JanMar...