3 ms·
HTTPS does not break caches; that's FUD. Browsers can cache HTTPS pages just fine, and do by default unless told not to. Nothing forces sites to use a CDN. H
by JoshTriplett 12y ago
HTTPS does not break caches; that's FUD. Browsers can cache HTTPS pages just fine, and do by default unless told not to.
Nothing forces sites to use a CDN. HTTPS, by itself, does not massively increase load. If the limiting factor of your web server is how fast you can do cryptographic operations for HTTPS, you're doing rather well; most of the time that won't be your limiting factor.
Using a CDN is not wildly less secure than using a hosting service, and numerous sites use hosting services. "Secure to the CDN" is still a net improvement over "completely insecure".
By all means, complain about sites using a CDN that you don't trust. That's not an argument against universal adoption of HTTPS, though.
- frankzinger 12y agoHTTPS does not break caches; that's FUD. Browsers can cache HTTPS pages just fine Yes, but caching by intermediaries is a very important part of HTTP caching, and HTTPS effectively breaks that, does it not?
- JoshTriplett 12y ago> Yes, but caching by intermediaries is a very important part of HTTP caching Proxies are not a common setup; approximately zero home users use them, and a subset of corporate networks do (only the obnoxious ones). In any case, caching proxies are far less important than caching browsers, and HTTPS does not in any way break caching browsers.