639136 - Persistent cookie value with high ASCII character is changed after browser restart

Status: RESOLVED INVALID

(Firefox :: Extension Compatibility, defect)

Description

[Simon]

User-Agent:       Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b12) Gecko/20100101 Firefox/4.0b12
Build Identifier: 4.0b12

When a cookie is written with a value that contains an unencoded high ASCII
character (above ASCII 127), the cookie value changed after a browser restart.

1þþþþþþþþþþþþöäu1

If this string is written as a cookie value, when Firefox 4.0 closes and you
reopen it, the cookie value becomes:

1��������������u1







Reproducible: Always

Steps to Reproduce:
1. Write a simple script to write a cookie with a value that contains a high
ASCII character.  Examine the cookie in FF 4.0 to verify how it was written.
2. Close FF 4.0
3. Open FF 4.0 and view the cookie again to see that is has been scrambled
Actual Results:  
1��������������u1
Cookie value is scrambled with the high ASCII characters.

Expected Results:  
1þþþþþþþþþþþþöäu1

Cookie value left as-is.

Comment 1

[Simon]

Attachment: Testcase

Simple Testcase, Restart the browser to see the uncorrect cookie values

Comment 2

[Ed Morley [:emorley]]

Did this work correctly in 3.6.x?

Comment 3

[Simon]

Yes it did.
There was a almost similar Bug(Bug 544496) which was fixed in 3.6.2.

Comment 4

[Alice0775 White]

I cannot reproduced,It seems to work for me.
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b13pre) Gecko/20110307 Firefox/4.0b13pre ID:20110307030403

Comment 5

[Bjarne (:bjarne)]

Maybe connected to the charset? Observe that if you add e.g.

<meta http-equiv="Content-Type" content="text/html; charset=utf-8">

to the provided test, it seems to work fine.

Comment 6

[Simon]

Hi again.
I found the cause. It is the add-on Xmarks 3.9.5 which causes that problem.
Opened a ticket @ xmarks.com.

Comment 7

[Ed Morley [:emorley]]

Thanks for the update.

Marking as invalid, since not a bug with Firefox.