question about private browsing andcookies in rel 3.6.6
I have been using Auto Private Browsing mode for the last 6 months and never had any problems before with accessing my banks online service. That is until I updated to Firefox 3.6.6. Before this problem started, when I went to my Banks website and entered my Username i was sent to another URL and asked to verify an Image so I could enter my password. Since updating to 3.6.6 every time I go to my banks website I am prompted to answer a security question and also asked if i want to save the info from this PC( so i don't have to answer a security question every time.) I would really like to stay with Private Browsing all of the time. I have tried entering ALL the websites that my bank uses in the Tools -> Options Privacy Tab -> Exceptions Tab to ALLOW from these websites. What appears to be happening now is that they are always deleted when I end a Firefox session. But allowed to be added when I start a FF session and go to my banks website(s). I would have assumed that if I was going to allow these Exception website to write cookies that they would not be deleted when I exited Firefox. I guess that's a wrong assumption, hey? How can I resolve this problem?
所有回复 (2)
Your Goal: Persist data from websites on your computer (your bank's offer to save information for your PC).
Private Browsing's goal: Prevent any persistence of information from websites, including that you've been to them at all.
If a website was able to have Firefox store cookies from a site in private browsing mode, that would appear after restarting Firefox or exiting Private Browsing, the feature would be completely worthless.
Don't use Private Browsing - Use Firefox without saving history if you want Firefox to save information (such as cookies, including the login token from your security question).
A reason I could think why this would stop working is you originally authorized a computer (browser, really) outside of Private Browsing and then this authorization expired.
Reply from Anonymous, I would agree with your comments except that I mentioned I have been using Private Browsing for the last 6 months and never had this problem before upgrading to 3.6.6 the other day.
Are you saying that Mozilla has finally fixed a bug that has been occurring since adding the Private Browsing capability? I didn't see anything in the Release Notes for 3.6.6 about this issue.