HTTPS can in fact be cached, and most modern browsers will do so unless given a header or something to tell it not to.
Source: Devtools network tab + developer.mozilla.org/en-US/docs/Web/…/Caching
Comment on SpaceX says states should dump fiber plans, give all grant money to Starlink
Cocodapuf@lemmy.world 17 hours agoOk, so actual question, How useful are CDN endpoints these days with https everywhere? Because you can’t cache encrypted content. Also you can’t cache live content like video calls or online games. I’d imagine the percentage of cacheable content is actually fairly low these days. But like I said, I don’t actually know the answer to this, i’d be curious to hear your take.
Xylight@lemdro.id 16 hours ago
ubergeek@lemmy.today 6 hours ago
Netflix and Amazon Outpost makes it quite useful.
randompasta@lemmy.today 9 hours ago
HTTPS / TLS has little to do with it. Don’t think of the endpoint as a cache between you and the origin. The DNS name given to the endpoint is the origin from your browser’s perspective. How content gets cached on the backend is irrelevant to the browser. Live video that someone else in your area is also watching is cacheable. Images to load a page, very cacheable. The personal stuff is mostly HTML specific to you but that’s quite small.