1220350 - Cookie Exceptions Regression in Firefox 42

Status: RESOLVED DUPLICATE of bug 1210379

(Core :: Permission Manager, defect)

Description

[fxbugzilla.cdr]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:41.0) Gecko/20100101 Firefox/41.0
Build ID: 20151015172900

Steps to reproduce:

Installed Firefox 42 (42.0+build2-0ubuntu0.14.04.1).  Running in private browsing mode (always enabled) with cookies disallowed.  Navigated to a page where I have a cookie exception in Preference->Privacy->Exceptions - Cookies.


Actual results:

Cookies were blocked and could not be allowed, despite the exception.  I had to globally enable cookies to get pages to work.  My exceptions disappeared from the preferences list, but I could still find them in permissions.sqlite.

When I tried to add a site again manually (despite me knowing it is already there), I could not add it in a way that was usable.  Trying to add "email-site.com" would force the exception to "http://email-site.com" when I need it to allow something more generic (e.g., "https://mail.email-site.com").  Cookies were still blocked in all cases.


Expected results:

Firefox should allow cookie exceptions I've set.  Firefox should show the exceptions I've set.  Downgrading back to Firefox 41.0.2 (41.0.2+build2-0ubuntu0.14.04.1) immediately fixed the problem.  My exceptions show up as normal, and I can visit pages and have cookies blocked or allowed as I have them set.

This is a temporary workaround at best since the downgrade opens me up to security vulnerabilities fixed in Firefox 42.

Comment 1

[Gingerbread Man]

Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:45.0) Gecko/20100101 Firefox/45.0
20151030030236

Push log:
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=15155971639c&tochange=d317a93e5161

Suspect: bug 1173523.


This isn't specific to Private Browsing, nor does it require having cookies disabled globally or existing cookie exceptions.

(In reply to fxbugzilla.cdr from comment #0)
> Trying to add "email-site.com" would force the exception to "http://email-site.com"
> when I need it to allow something more generic (e.g., "https://mail.email-site.com").
> Cookies were still blocked in all cases.

Also, entering http://*.foo.bar and https://*.foo.bar works, but the exceptions have no effect.