Where are my SpywareBlaster Cookies - Exceptions
Happened to notice my SpywareBlaster Cookies - Exceptions are missing in action. Don't know when they went missing. I've created new profiles with profile.exe -p and FEBE expecting to find all my cookies exceptions and then I'd compare profiles to see what file is missing. Well, new profiles are as bare as default profile. I've done SpywareBlaster uninstall/install thingy with no joy. I've done SB Enable All Protections thingy with no joy. I'm running Firefox42x64 on W8.1x64. Maybe cookie exceptions went missing upon FF42x64 install. Perhaps 42x64 is not officially supported. I've heard 42x64 users have SpywareBlaster cookies exceptions...so, I must have done something. Anyone recall FF users with missing SpywareBlaster Cookies - Exceptions or missing user created cookie exceptions. Anyone know where the exceptions reside in my profile.... e.g., cookies.sqlite...?
All Replies (3)
maybe it takes time for op message to show edit option... so, here's second screenshot
Exceptions like the cookie permissions are stored in permissions.sqlite. In case you use "Clear history when Firefox closes" or otherwise clear history.
- do not clear the Site Preferences
- Clearing "Site Preferences" clears all exceptions for cookies, images, pop-up windows, software installation, passwords, and other website specific data.
cor-el said
Exceptions like the cookie permissions are stored in permissions.sqlite. In case you use "Clear history when Firefox closes" or otherwise clear history.
- do not clear the Site Preferences
- Clearing "Site Preferences" clears all exceptions for cookies, images, pop-up windows, software installation, passwords, and other website specific data.
Okay, as a matter of long practice. I do not clear Site Preferences. As a matter of long practice I'll clear Browsing & Download History but, not Site Preferences. Data is not cleared as a matter of long practice. Any idea how to can get permissions.sqlite to populate exceptions...? I've re-created permissions.sqlite with no joy.
Um, since we're talking Site Preferences. How about "prefs" / "prefs.js" ...?
Modified by bjm_