W3C home > Mailing lists > Public > www-tag@w3.org > January 2015

Re: Draft finding - "Transitioning the Web to HTTPS"

From: Mark Nottingham <mnot@mnot.net>
Date: Tue, 20 Jan 2015 08:39:29 +1100
Cc: Henri Sivonen <hsivonen@hsivonen.fi>, David Sheets <kosmo.zb@gmail.com>, Noah Mendelsohn <nrm@arcanedomain.com>, Tim Berners-Lee <timbl@w3.org>, Public TAG List <www-tag@w3.org>
Message-Id: <24028CF3-08F4-4974-860C-65BE9381E240@mnot.net>
To: Mark Watson <watsonm@netflix.com>
Hi Mark,

I saw that last year. It's disturbing that the people who regulate technology either fundamentally misunderstand it, or purposefully misinterpret it.

HTTP caching is not mandated, it's an optimisation, and content providers are given explicit controls over it by the protocol (as per <http://httpwg.github.io/specs/rfc7234.html>). The "allegations" should be more about how some networks disregard these controls and cache things against content providers' wishes.

Neither Cache-Control nor HTTPS is "undermining standards" -- it's utilising them. 

Cheers,


> On 17 Jan 2015, at 7:45 am, Mark Watson <watsonm@netflix.com> wrote:
> 
> While we are on the subject of caching, we have the interesting spectacle here in the US [1] of an FCC Commissioner calling interception proxies "open caching" and arguing against user privacy protections that, as a side-effect, impede such caches.
> 
> …Mark
> 
> [1] http://arstechnica.com/business/2015/01/netflix-refused-to-answer-encryption-allegation-fcc-commissioner-says/

--
Mark Nottingham   https://www.mnot.net/
Received on Monday, 19 January 2015 21:40:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:57:09 UTC