3 ms·

I figured this out yesterday while working on a client's site. Apparently FF private mode still uses existing cache. If you had files from the site cached befor

I figured this out yesterday while working on a client's site. Apparently FF private mode still uses existing cache. If you had files from the site cached before opening the site in private mode it will still use them. This seems like a pretty big issue to me. It defeats private mode.

northwest 13y ago
Same here. This is definitely not ok. EDIT 1: I also checked "Clear history when Firefox closes" and included "Cache" in the definition of "history". And the tracking is still happening. So either the site uses another tracking method in addition to the etag method or there is a big f#ck-up in FF. EDIT 2: The tracking even continues when I check "Always use private browsing mode" and then close the browser and open it again. EDIT 3: Even a complete removal and a clean install of FF (without any add-ons which may interfere) lets the tacking happen, for both the case of "EDIT 1" and "EDIT 2". So this pretty certainly seems to be a bug.
- northwest 13y ago
  EDIT 4: Even having set about:config -> browser.cache.disk.enable -> false, I have to close/open the browser twice in order for the cache (and tracking) to disappear.
- kfcm 13y ago
  The only way I've found to ensure this doesn't happen is to set about:config -> network.http.use_cache = false. Private browsing keeps it for at least one restart (with clear everything set in options), even though I can't see tracker.jpg in about:cache anywhere. Other weird thing is tracker.jpg isn't showing up in a filesystem search anywhere. Wondering if there's something stored in the sqllite files.
  - northwest 13y ago
    That works, thanks!
deleted 13y ago
[deleted]
Gurrewe 13y ago
Private browsing-modes "forks" the current state of the browser instead of creating a new "blank" state. And it's this way by design.
- Groxx 13y ago
  If that were true, why am I not logged into sites when I start a new private window? If it is true, then that's hugely non-obvious, given the behavior (being logged out). That's bad design, plain and simple.

northwest 13y ago

Same here. This is definitely not ok. EDIT 1: I also checked "Clear history when Firefox closes" and included "Cache" in the definition of "history". And the tracking is still happening. So either the site uses another tracking method in addition to the etag method or there is a big f#ck-up in FF. EDIT 2: The tracking even continues when I check "Always use private browsing mode" and then close the browser and open it again. EDIT 3: Even a complete removal and a clean install of FF (without any add-ons which may interfere) lets the tacking happen, for both the case of "EDIT 1" and "EDIT 2". So this pretty certainly seems to be a bug.

northwest 13y ago
EDIT 4: Even having set about:config -> browser.cache.disk.enable -> false, I have to close/open the browser twice in order for the cache (and tracking) to disappear.
kfcm 13y ago
The only way I've found to ensure this doesn't happen is to set about:config -> network.http.use_cache = false. Private browsing keeps it for at least one restart (with clear everything set in options), even though I can't see tracker.jpg in about:cache anywhere. Other weird thing is tracker.jpg isn't showing up in a filesystem search anywhere. Wondering if there's something stored in the sqllite files.
- northwest 13y ago
  That works, thanks!

deleted 13y ago

[deleted]

Gurrewe 13y ago

Private browsing-modes "forks" the current state of the browser instead of creating a new "blank" state. And it's this way by design.

Groxx 13y ago
If that were true, why am I not logged into sites when I start a new private window? If it is true, then that's hugely non-obvious, given the behavior (being logged out). That's bad design, plain and simple.