This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

ابحث في الدعم

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Cookies and site data exceptions

  • 7 ردود
  • 2 have this problem
  • 2 views
  • آخر ردّ كتبه Red-Herring

more options

Hello,

I am having bit of a problem with the cookies in the latest Firefox 69 and the 69.0.1 update that I had just now. In the Firefox I had Cookies and site data permissions set to allow specific sites for the current session and now after the update looks like those cookies are getting blocked... I always have been using private mode and I had disabled all the cookies. Looks like a bug, right? I think I could try add exceptions to the Content blocking, but then again, other stuff apart from cookies will be allowed. Running browser in the safe mode gives same result.

I would appreciate some help to resolve that issue. Thank you.

Hello, I am having bit of a problem with the cookies in the latest Firefox 69 and the 69.0.1 update that I had just now. In the Firefox I had Cookies and site data permissions set to allow specific sites for the current session and now after the update looks like those cookies are getting blocked... I always have been using private mode and I had disabled all the cookies. Looks like a bug, right? I think I could try add exceptions to the Content blocking, but then again, other stuff apart from cookies will be allowed. Running browser in the safe mode gives same result. I would appreciate some help to resolve that issue. Thank you.

الحل المُختار

No change after updating to version 70.0...

Update: Found a solution! I had a "privacy.firstparty.isolate" option set to "true" long time ago, that was causing the problem in FF 69 an up. Switching it to default (false) solves the problem.

Read this answer in context 👍 0

All Replies (7)

more options

Adding exceptions in the "Content Blocking" section would indeed completely disable Content Blocking on the specific websites.

However, you should in theory still be able to add permissions under the "Cookies and Site Data" section that still exists within the Firefox settings. In theory again, you should be able to stay under "strict" Content Blocking for all sites while allowing cookies and site data for a set of choosen websites for the current session via the permissions in the "Cookies and Site Data" section .

Are the permissions that you set up before updating to Firefox 69 still present now that you have Firefox 69? If not, did you try setting them up again?

Sorry if you have done all this already but sometimes it is worth asking.

more options

An allow exception for cookies isn't restricted to cookies, but is applied to a lot more permissions for this domain. You set an allow exception for a specific domain and this includes cookies.

See also the Storage Inspector.

more options

@elched Yes, those permissions are still present. I did try to set them one of them up again, but it didn't work. I have also tried to create a new one, but it didn't work either.

@cor-el I know that, I just wanted them to work on the sites that I want give permissions to. I guess people are usually doing the opposite and generally have their cookies setup to allow all cookies with the default Firefox settings (now in FF 69 external cookies aren't allowed on default) and blocking whatever they need to. I am blocking everything and adding the exceptions to allow cookies and site data, but it doesn't do anything anymore since FF 69 update.

more options

I had the same problem and ended up going back one version to 68.0.2. It looks like the Manage Permissions table under Cookies and Site Data is ignored.

more options

Did you make sure that you add the correct protocol (https:// or http://) to the URL if you create the allow exception manually ?

You may also have to create the exception for the top level domain without the www. or other prefix like https://google.com

more options

@JD Exactly.

@cor-el I used copy-paste, and yeah, I have used top level in most cases when needed.

more options

الحل المُختار

No change after updating to version 70.0...

Update: Found a solution! I had a "privacy.firstparty.isolate" option set to "true" long time ago, that was causing the problem in FF 69 an up. Switching it to default (false) solves the problem.

Modified by Red-Herring