Re:Firefox 83 introduces HTTPS-Only Mode
by cat199 on Tuesday November 17, 2020 @08:54AM
(#25123721)
this breaks caching of simple objects that do not require content security
Re:Firefox 83 introduces HTTPS-Only Mode
by taftster on Tuesday November 17, 2020 @09:55AM
(#25124361)
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.
Re:Firefox 83 introduces HTTPS-Only Mode
by cat199 on Saturday November 21, 2020 @07:36PM
(#25173829)
speaking specifically of local package caches for things like onsite networks which are themselves signed OOB
Re:Firefox 83 introduces HTTPS-Only Mode
by new23d on Tuesday November 17, 2020 @09:47AM
(#25124269)
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.
Re:Firefox 83 introduces HTTPS-Only Mode
by wang_li on Tuesday November 17, 2020 @11:15AM
(#25125466)
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.
Re:Firefox 83 introduces HTTPS-Only Mode
by jlgaddis on Wednesday November 18, 2020 @07:16AM
(#25135933)
> 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]
--
Re:Firefox 83 introduces HTTPS-Only Mode
by SulfurHexaFluri on Tuesday November 17, 2020 @05:19PM
(#25130690)
The browser can still see everything and still cache whatever it wants. Safari and likely others are turning off cross site caching anyway.
I work for a firewall co and we had taken a strategic decision to not allow plaintext traffic onto the internet (from cloud deployments). It's just lazy on the client or server operator's part to not have it so.