Hacker News Reader

Comment by cat199 | Hacker News Reader

this breaks caching of simple objects that do not require content security

Even "simple objects" can be MITM'd. I know I'm on the extreme theoretical edge, and so maybe your perspective is pragmatic enough to pass. But even small images, javascripts, etc. should be protected by HTTPS, not just "sensitive" pages.

As an end user, I don't want the possibility of anything being tampered with along the route. As a content owner / webmaster, I want the same. So publisher and consumer are both aligned in their desire, making HTTPS ideal for everyone except for people reading/manipulating traffic along the way.

speaking specifically of local package caches for things like onsite networks which are themselves signed OOB

From intermediate (MITM) caches, yes. But end-clients can still cache it though.

Our market is more backend API traffic so doesn't impact as much.

Since it's becoming harder and harder to implement transparent proxies and caches, someone should define a local cache protocol so that network administrators can configure explicit shared caches for the devices on their networks.

> someone should define a local cache protocol

Someone did, almost two and a half decades ago. It's called the Internet Cache Protocol.

- Internet Cache Protocol (ICP), version 2 [0]

- Application of Internet Cache Protocol (ICP), version 2 [1]

[0]: https://tools.ietf.org/html/rfc2186

[1]: https://tools.ietf.org/html/rfc2187

The browser can still see everything and still cache whatever it wants. Safari and likely others are turning off cross site caching anyway.

HTTP != browser always

Reply on news.ycombinator.com