© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
(In reply to comment #21)
> I can reproduce this issue quickly and easily on my system.
>
> Steps to reproduce:
>
> 1) Either start from a new profile, or do a "Clear Recent History" with
> time range "Everything" and at least the "Cookies" box checked
> followed by running "sqlite3 cookies.sqlite vacuum".
>
> 2) Run "strings cookies.sqlite | grep -i google", and observe that no
> results appear.
>
> 3) Open Firefox, and visit google.com. Close Firefox.
>
> 4) Run "strings cookies.sqlite | grep -i google", and observe that some
> results appear, as expected.
>
> 5) Open Firefox. Do a "Clear Recent History" with time range
> "Everything" and at least the "Cookies" box checked. Close
> Firefox.
>
> 6) Run "strings cookies.sqlite | grep -i google", and observe that the
> results from step 4 still appear, despite having cleared cookies.
Have you also tested this with some other domain than google.com?
The problem is that if between steps 5 and 6 there were some hidden connections to Google (eg. related with so-called "safebrowsing"), then the google cookie "magically" reappears.
Here are steps to reproduce (I haven't reported it as a separate bug, as it is part of bug 368255, I guess -- and the real fix of this bug is apparently not wanted - see comments and history of that bug):
1) run Firefox on default settings (in particular make sure that you have one of the "safebrowsing" related options checked in UI, ie. either "Block reported web forgeries" or "Block reported attack sites", or both (as is default))
2) open cookie manager, you should see cookie from google.com (if not - visit google.com or other Google-related site)
3) close all tabs, go to about:blank (just to be sure...)
4) remove all cookies or only cookie from google.com
5) close and reopen cookie manager, just to make sure that google cookie is gone
6) having only about:blank loaded wait at most half an hour (don't use browser at all during this time, just keep its window opened (minimized))
7) check cookie manager again - you'll notice google.com cookie again - it was silently set during hidden "safebrowsing" related connections.