News for hackers. Stuff that matters.
Re:Decentraleyes: A Firefox addon to prevent tracking via fr... by vbezhenar on Monday February 01, 2016 @03:11AM (#11010467)
I thought that CDN should send proper caching headers and browser will save cached version after first request and never hit CDN again.
Re:Decentraleyes: A Firefox addon to prevent tracking via fr... by sametmax on Monday February 01, 2016 @03:28AM (#11010515)
They do but the browser has a limited cache size. And because of the gigantic size of even the smallest web sites these days, the cache is maxed every day, and your file are purged again and again. This is basically just a super cache of files you know you never want to invalidate. Also, it prevents OPTIONS and HEAD requests.
Re:Decentraleyes: A Firefox addon to prevent tracking via fr... by morsch on Monday February 01, 2016 @06:20AM (#11011101)
Are browsers really this stupid? Seems like an obvious strategy to have several cache buckets, with one dedicated to smaller assets with long expiry times.
Re:Decentraleyes: A Firefox addon to prevent tracking via fr... by sametmax on Monday February 08, 2016 @09:27AM (#11058220)
It's not stupidity. There is really no way to know which file you want to keep longer than others without risking breaking things. CDN are actually a good, manually updated, source of listing of files that have this quality. But basing yourself on proprietary CDN are not a move any browser in their right might would do.
Re:Decentraleyes: A Firefox addon to prevent tracking via fr... by inanutshellus on Monday February 01, 2016 @09:11AM (#11011797)
That it has been looked at at /any level/ (e.g. this plugin) is great, and it does so without waiting for a decade of W3C and browser standards back-and-forth.
Re:Decentraleyes: A Firefox addon to prevent tracking via fr... by perlpimp on Monday February 01, 2016 @03:23AM (#11010504)
still need to check if file is changed, hence 304 http status code.
Re:Decentraleyes: A Firefox addon to prevent tracking via fr... by mike-cardwell on Monday February 01, 2016 @05:23AM (#11010921)
If the server sends an "Expires" header in the response, then the client doesn't even need to do that check. With an expires header, the server has effectively told the client that the data wont change until at least a particular date, and so the client honours that information.

Last-Modified/If-Modified-Since is an optimisation trick which exists for the situation where the person running the website hasn't bothered to explicitly define expiry periods for content.

Re:Decentraleyes: A Firefox addon to prevent tracking via fr... by SahAssar on Monday February 01, 2016 @03:33AM (#11010539)
That depends on what type of caching headers the CDN uses. If it uses max-age and no etags/last-modified the browser won't send the if-modified-since request and just use the cached resource without asking the server.