Re:Do not let your CDN betray you: use subresource integrity...
by zrm on Wednesday April 05, 2017 @01:35PM
(#14043884)
Possible solution is to have a content hash proxy trusted by the user but shared between multiple users. Then the site can only get the data at the proxy-level rather than the user-level, and not even that if the proxy is large enough to justify crawling the web to pre-cache everything, or is behind a larger cache that does.
[ Parent
| on HN ]
Re:Do not let your CDN betray you: use subresource integrity...
by nothrabannosir on Wednesday April 05, 2017 @02:07PM
(#14044190)
That's not a solution but a work-around. The original privacy issue stands. browsers can't cache hashed content by default. :/
Re:Do not let your CDN betray you: use subresource integrity...
by zrm on Wednesday April 05, 2017 @02:45PM
(#14044493)
The browser would know if it had a content hash proxy configured and then could use it for all content hashed data. The issue becomes getting people to use one, but partial uptake is better than nothing. You could at least get most corporate and education environments with some equivalent to WPAD[1], and maybe even some consumer-level ISPs the same way if they want to reduce the traffic over their network.
[1] https://en.wikipedia.org/wiki/Web_Proxy_Auto-Discovery_Proto...