After submit , the value is changed. May be a character problem about edit-this-cookie HOT 7 CLOSED

From [email protected] on May 17, 2012 08:34:21
hello? any body in home ??!

from edit-this-cookie.

From [email protected] on May 17, 2012 13:53:34
As you can read here: http://stackoverflow.com/questions/1969232/allowed-characters-in-cookies and here: http://curl.haxx.se/rfc/cookie_spec.html the cookie name and value cannot contain special characters. They can't contain semi-colons, commas, white spaces, and '='.
I believe this is not a bug

from edit-this-cookie.

From [email protected] on May 19, 2012 09:05:56
what? no! are you kidding. may be you think can't contain, but some people used. come on,fixed it. Even can't contain , you can't decide this. Previous version it's good. but now because of this, the server can't Normal analytic this cookie. if you have to, you can add a option, can't decode coockie value. please.

from edit-this-cookie.

From [email protected] on May 19, 2012 09:11:06
you can add a option encode coockie value or not before submit.

from edit-this-cookie.

From [email protected] on May 21, 2012 01:20:41
are you plan fix this or not ??

from edit-this-cookie.

From [email protected] on June 14, 2012 16:34:08
Re comment 2: none of the information you pointed at disallows = in the value, only in the name (quoting the stackoverflow answer: "By implication the = character is also disallowed in the name part").

The RFC allows = in the value as well:
http://tools.ietf.org/html/rfc6265#section-4.1.1

from edit-this-cookie.

From [email protected] on June 22, 2012 14:35:58
I'll investigate it further, meanwhile the upcoming update will include an option to disable encode on value

from edit-this-cookie.