3 ms·
The plugin mentioned at the end won't work - not unless it's going to have a tedious whitelist. Since many sites use "3rd party requests" like remotely hosted
by ck2 15y ago
The plugin mentioned at the end won't work - not unless it's going to have a tedious whitelist.
Since many sites use "3rd party requests" like remotely hosted images, fonts, and even for example google based jquery, blocking them would most certainly break the page.
What I would like is a warning when the last-modified appears to be a malformed date or not a date at all. PHP's strtotime can convert almost anything to a date/time (if it really is a date). Can it be ported? Optionally when it doesn't appear to be a date within the past 30 days, never cache it.
Another solution for a pure privacy mode is to never send back last-modified, ever. It would hurt servers and page load times because things would never be cached and always served as "200" instead of "304" but for a pure privacy mode, may be necessary.
Last but not least, we could just dial down our cache time limit to say an hour max. It would still give some info to the trackers but not between browser sessions or the computer turned off. Since firefox doesn't have a time limit on the cache, using a memory-only cache is the only easy workaround for now.
- sirclueless 15y agoKilling the If-Modified-Since header probably doesn't substantially increase privacy compared to alternatives. Remember, the header doesn't stick around unless the browser caches the response anyways. For example, Google Chrome's incognito mode kills this cached "cookie" along with all other legitimate cookies when you close your browser (clearing the cache), just as you expect with other cookies.
- mike-cardwell 15y agoRe blocking 3rd party requests. There is already a well known Firefox addon which does this called RequestPolicy. If you have the patience to spend 10 seconds training it the first time you visit each new website, it protects you from all sorts of bloat, tracking and xss/csrf issues.
- justincormack 15y agoHttp defines the date format precisely (although there are 3 valid formats) and browsers already can parse it for other purposes, like cache expiry. http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html I imagine this bug will be fixed pretty quickly as the http replies being sent are out of spec.
- copypasteweb 15y ago>The plugin mentioned at the end won't work - not unless it's going to have a tedious whitelist. RequestPolicy (Firefox addon) works just fine, not much tedious than NoScript or CookieMonster, for example. While remotely hosted images may be a strong argument, if the page breaks due to missing fonts or scripts - it's really only site's fault.