3 ms·
Given that "currently no browser supports HTTP/2 unencrypted" they're inseparable in the real world. https://http2.github.io/faq/#does-http2-require-encryption
by CiPHPerCoder 9y ago
Given that "currently no browser supports HTTP/2 unencrypted" they're inseparable in the real world.
https://http2.github.io/faq/#does-http2-require-encryption https://http2.github.io/faq/#does-http2-require-encryption
- tptacek 9y agoRight, but enabling TLS on an HTTP/1.1 site isn't going to generate that performance improvement. It's a bogus comparison.
- CiPHPerCoder 9y agoOh, I see what you mean. The relationship doesn't work both ways, and the benchmark might lead one to believe it does.
- tokenizerrr 9y agoSo it's a http2 vs http1 benchmark. Not a http vs https benchmark?
- CiPHPerCoder 9y agoRight. HTTP/2 is only available with TLS, due to browser policies, so it necessarily requires TLS. This means you need HTTPS if you want the performance wins of HTTP/2. This doesn't mean that HTTPS is a performance win if you're still using HTTP/1.1. However, the "performance overhead" for TLS is negligible in practice.
- tptacek 9y agoYes, so there are two major changes you'd need to get this performance benefit, not one, and if you just make the TLS change, your performance will (probably marginally) suffer, not improve. It's a bogus comparison.
- tzahola 9y agoDidn't you know that air fresheners make cars go faster? Just look at my Ferrari F450 with an freshener vs this Nissan Micra without one!