User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:184.108.40.206) Gecko/20091102 Firefox/3.5.5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:220.127.116.11) Gecko/20091102 Firefox/3.5.5 This seems to be commonly reported with the exceptions list disappearing "bug" which seems to have a "resolution," but it is a separate issue. When I add a cookie to the exceptions list as "blocked" and delete that cookie from the list of cookies, the next time that cookie is sent it reappears in the cookie list even though it is "blocked" in the exceptions" list. Luckily my anti-virus software catches the bad ones when they "reappear" but I would expect the blocked cookie never to even make it to the cookie list. In addition in trying different things, it appears that some cookies still get through even when I uncheck the "accept cookies from sites" button. Could these problems be related? Reproducible: Always Steps to Reproduce: 1.Add cookie to the exceptions list as blocked. Delete that cookie from the list of cookies. 2.Go to a site with that cookie 3.Blocked cookie shows up again in cookies Actual Results: as above Expected Results: Blocked cookies in exception list should not be accepted. This would seem to be a fairlysevere security issue as there are some notorious cooies out there.
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:18.104.22.168pre) Gecko/20091208 Shiretoko/3.5.7pre I tested this (www.google.com) but was not able to reproduce.
Component: Security → General
QA Contact: firefox → general
Version: unspecified → 3.5 Branch
Hi: Most odd as it is consistent here and has been reported elsewhere. Could some module or file in my FF 3.5.5 install be corrupted? Would it be worth totally deleting all FF files (backing up my bookmarks as a minimum) and then reinstalling from a clean download, or perhaps just reinstalling the current build?
Hi again: Another followup. I tried testing with Google as you did and the cookie showed up. On an off chance I reinstall FF on top of the original on my PC and then tried it again and it appears that (at least for Google) the cookie was blocked. Any thoughts on what might have been corrupted? You can probably close this report, although there appears to be other instances of such behavior reported in other bugs. John S.
Thanks for reporting back. The reinstallation could have replaced corrupt files in your installation directory. Every other program that you permit to run can install or change files in the Mozilla Firefox folder. Resolving Worksforme. Please reopen if the issue reoccurs.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.