When will there be a fix for cookies glitch in Firefox 42.0?
Firefox 42.0 has disabled the function of have exceptions to cookies blocking.
In the previous version, 41.0.2 you can block cookies generally then allow cookies for specified "exceptions".
In the new version, you can set "exceptions" but it has no effect. Cookies continue to be disallowed unless you allow cookies fore every site.
This issue was identified by another person at https://support.mozilla.org/en-US/questions/1093413#answer-806550
I tried refresh, safe mode, and a complete uninstall with every firefox file deleted from my computer and nothing had an effect. There was no way to get the "exceptions" to allow cookies. Only allowing all cookies would work.
Reinstalling the old version immediately restored the ability to disallow cookies generally but still allow for exceptions (specified sites).
All Replies (6)
You don't mention your Cookie Controller extension. There could be a conflict with Fx 42. You could try disabling this extension and see how Firefox copes on its own. If that doesn't help, you could investigate Cookie Controller further. I've noticed comments that it is too complicated.
A little housekeeping. You have Adobe PDF Plug-In For Firefox and Netscape 10.1.16 Adobe PDF Plug-In For Firefox and Netscape "9.5.5" Remove the older one.
Modified by alan_r
i only put cookie controller extension on after the other steps i took. i.e. after safe mode, refresh and complete uninstall / delete / reinstall.
Therefore the problem is clearly with the update - completely unrelated to cookie controller extension. it works perfectly with the old version (whether i ham using cookie controller or not). i only put cookie controller on to help me deal with all the craziness of managing this huge huge problem the update has caused. Suddenly i need quick access to cookie settings and it provides that.
I really hope that firefox will fix this because privacy settings is one of the main reasons i use firefox. i don't want to use the old out of date less secure version. Can't they just fix it?
I found a solution!
If you put the site exception in both of these formats, it works!
http://mozilla.org https://mozilla.org
Either one on its own does not work. This is new with the update, it didn't used to matter what format you used. Ideally they will still adjust this as I can imagine others like me have been turned around in circles by this!
I hope this info helps other people. Best wishes to all.
It seems that the permissions system no longer refers to bare host names, but includes the protocol. When I open the Permissions Manager (type or paste about:permissions in the address bar and press Enter) I see those protocols now in the left column, as well as in the Exceptions dialog.
It's a little puzzling that you need to add two exceptions if you are only using one of the protocols for the site. I haven't tested it myself. Maybe someone needs to file a bug report on that (https://bugzilla.mozilla.org/).
I see all cookies when I check a specific item like Google (http://google.com and https://google.com). The cookies that I have for mail.google.com are all for encrypted connections, but all other Google entries show the cookies for any type of connections and cookies for encrypted connections only, so I don't know where or whether this makes a difference. I would expect that if you leave out the protocol that the exception would work for all types of connections.
cor-el said
I would expect that if you leave out the protocol that the exception would work for all types of connections.
No, leaving out the protocol does not make exceptions to cookie blocking work.
For example if you enter "amazon.com" into exceptions, FF records it as "http://amazon.com", and, until you then also add "https://amazon.com" FF will continue to block the site's cookies.
The only way (for me anyway) to make the exceptions work (in this new update of FF) is to put both formats in for the site. Only then will it accept the site's cookies.