- From: Slim Amamou <slim@alixsys.com>
- Date: Wed, 20 Jan 2016 20:51:16 +0100
- To: Brad Hill <hillbrad@gmail.com>
- Cc: public-webappsec@w3.org
thanks. I'll dig the archive and come back On Wed, Jan 20, 2016 at 6:32 PM, Brad Hill <hillbrad@gmail.com> wrote: > It is a long term goal, but it was removed in favor of moving ahead with > something. There are a number of subtle issues to resolve for caching > around privacy and security that a careful scan of the mailing list will > reveal. There is continued interest in moving ahead with these ideas if we > can find solutions to the outstanding problems. > > On Wed, Jan 20, 2016 at 4:16 AM Slim Amamou <slim@alixsys.com> wrote: >> >> Hi, >> >> I read the SRI spec https://www.w3.org/TR/SRI/ >> >> and I thought that SRI would solve the main problem we have with HTTPS >> in developing world : it breaks caching through proxies. Bandwidth is >> not cheap for the developing world, and caching proxies are designed >> to solve specifically that problem. >> >> So my suggestion would be to add Improving usage of Caching Proxies as >> a goal in the next release. >> >> But I just saw that improving caching (in the browser) as a goal, was >> removed from an earlier version of the draft : >> >> https://www.w3.org/TR/2014/WD-SRI-20140318/#goals-1 >> >> is there a reason for this? I did not find the answer in the mailing >> list archive >> >> -- >> Slim Amamou | سليم عمامو >> http://alixsys.com >> > -- Slim Amamou | سليم عمامو http://alixsys.com
Received on Wednesday, 20 January 2016 19:51:43 UTC