If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

cookie clear when browser closes ignoring user preference

VERIFIED WORKSFORME

Status

()

Core
Networking: Cookies
--
major
VERIFIED WORKSFORME
9 years ago
3 years ago

People

(Reporter: sheridan101, Unassigned)

Tracking

1.9.0 Branch
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10 (.NET CLR 3.5.30729)

summery says it all. i set my cookies to "save till expire" yet i close my browser and lo and behold all my cookies are gone. and i have to sign in again to all sights that should remember me

Reproducible: Always

Steps to Reproduce:
1.set option/privacy/cookies to accept and keep untill they expire
2.go to a sight that requires logon and sets a cookie
3.allow it to set cookie
4.close browser
5.restart browser
6.visit site that should remeber you because of set cookie
7.wonder where you cookie went
8.fill out bug report
Actual Results:  
cookies cleared open browser closing

Expected Results:  
cookies should have not been cleared
Can you please go to about:config and post back the values for the below preferences:

* privacy.sanitize.sanitizeOnShutdown
* privacy.item.cookies
Version: unspecified → 3.0 Branch
(Reporter)

Comment 2

9 years ago
i'm kind of a noob. i don't know how to do that.
It's easy.  Open a new tab, and enter "about:config" (without the quotes) into it and press Enter.  Then, click the "I'll be careful, I promise" button.  Then, type "privacy.sanitize.sanitizeOnShutdown" (without the quotes) inside the Filter text box above that page, and let me know what you see under the Value column.  After that, clear the Filter text box and enter "privacy.item.cookies" into it, and again look under the Value column and let me know what you see there.

Thanks!

Updated

9 years ago
Component: Private Browsing → General
QA Contact: private.browsing → general

Updated

9 years ago
(Reporter)

Comment 4

9 years ago
privacy.sanitize.sanitizeOnShutdown;false

privacy.item.cookies;false

hope thats helpful
OK, this nullifies one of my assumptions, so it was helpful!  :-)

Have you actually verified that no cookie exists after restarting Firefox by going to Tools > Options > Privacy > Show Cookies?

What is the value of the "Keep until" drop-down box in the Privacy tab of the Options window?
(Reporter)

Comment 6

9 years ago
yes i verfied it
 keep until pull down is set at "they expire"
OK, I'm out of ideas here.

Moving to the Cookies component and marking as qawanted.
Component: General → Networking: Cookies
Keywords: qawanted
Product: Firefox → Core
QA Contact: general → networking.cookies
Version: 3.0 Branch → 1.9.0 Branch
You should ask for help on http://support.mozilla.com

If only cookies aren't getting saved (but other preferences do, such as changing your homepage) you might have a corrupt cookies file

http://support.mozilla.com/en-US/kb/cannot+log+in+to+websites#Remove_corrupt_cookies_file
(Reporter)

Comment 9

9 years ago
that fixed it thank you
(Reporter)

Comment 10

9 years ago
sorry hit comment too soon....
yes that fixed it the main reason i posted it here instead of going to the help site is A)it had never happened to me before B)it happened right after firefox updated.
but as i said all fixed thanks for the help
(Reporter)

Updated

9 years ago
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
I am glad your issue has been resolved, but that makes this bug WORKSFORME. FIXED is only for a bug that has had a known patch checked into the tree, which has not happened in this case.
Status: RESOLVED → VERIFIED
Resolution: FIXED → WORKSFORME
Issue is Resolved - removing QA-Wanted Keywords - QA-Wanted query clean-up task
Keywords: qawanted
You need to log in before you can comment on or make changes to this bug.