Reply to post: Cacheualty

Mozilla returns crypto-signed website packaging spec to sender – yes, it's Google

Nick Kew

Cacheualty

There's quite a lot to address that, going as far back as HTTP/1.1 and the cacheing framework the Web grew up on. Dynamic content and third-party caches is a long-solved problem.

What HTTPS solves is the malicious MITM. The entirely benign cache is a casualty.

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon