The Firefox web browser ships with options to blacklist or whitelist domains to either block cookies a domain tries to save on the system or to allow cookies so that they can be saved to the system. That’s useful to block tracking cookies for instance or to allow cookies to be set by your favorite sites to make sure they are always saved even if you have selected to not allow cookies from all the other sites on the Internet.
To configure the blacklist or whitelist click on the Firefox button at the top and select Options from the menu that opens up. You can alternatively press Alt to bring up the menubar and select Tools > Options this way. When you are in the options switch to the Privacy tab and locate the Exceptions button next to cookies. Note that you only see that if you select Use custom settings for history under Firefox will on the page.
A click on Exceptions opens another window where web addresses can be whitelisted or blacklisted. Here you can also manage existing cookie exceptions as they are all listed in a table in the window. As far as exceptions go, you can block websites so that cookies won’t be saved anymore even if they try to set cookies, or allow cookies permanently or only for browsing sessions.
The latest Firefox update to version 17.0, and maybe even earlier than that in regards to beta, aurora and nightly versions of the browser, has somehow corrupted the cookies exception feature in Firefox.
While it is still possible to add web addresses to the exceptions list, you will notice that Firefox will not save the exceptions anymore. When you close Firefox and reopen it again, you will notice that the previously added exceptions are not there anymore.
They stay only for the browsing session, and you can close and reopen the exceptions window to check that this is the case. As soon as you close the browser and reopen it again, the exceptions are no longer listed here in the menu.
A Firefox support thread over at the official Mozilla Support site indicates that multiple users are having the same issue. The only viable option for now seems to be to downgrade the browser to 16.0.1 instead which behaves exactly as it should be in regards to saving cookies exceptions in the browser.
Have you noticed any issues with cookies exceptions in Firefox 17 or newer?
Update: Deleting the permissions.sqlite file in the Firefox proflie directory resolves the issue. The easiest way to get there is to enter about:support in the browser’s address bar. Locate the show folder button under Application Basics and click on it. Close Firefox afterwards, delete the permissions.sqlite file, and restart the browser.
DIGITAL JUICE
No comments:
Post a Comment
Thank's!