search

alooi14 / editthiscookie

Automatically exported from code.google.com/p/editthiscookie
0 stars 0 forks source link

After submit , the value is changed. May be a character problem #37

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Add a New Coockie 
2. Add value
3. Submit Coockie Change

when i'm click "Submit Coockie Change", the Cookie Value is Change , lost 
something like "=" is changing ,changing to like "%3D" .then the server can't 
Identification the cookie. the porblem is long time ago fixed, but now it's 
come back. what's wrong you programmers ?, i'm a programmer to ,don't Repeated 
that stupid mistake.

the version is : 0.14.8

Original issue reported on code.google.com by huangjin...@gmail.com on 15 May 2012 at 6:08

GoogleCodeExporter commented 8 years ago 
hello? any body in home ??!

Original comment by huangjin...@gmail.com on 17 May 2012 at 8:34

GoogleCodeExporter commented 8 years ago 
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

Original comment by fcap...@gmail.com on 17 May 2012 at 1:53

GoogleCodeExporter commented 8 years ago 
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.

Original comment by huangjin...@gmail.com on 19 May 2012 at 9:05

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
you can add a option encode coockie value or not before submit.

Original comment by huangjin...@gmail.com on 19 May 2012 at 9:11

GoogleCodeExporter commented 8 years ago 
Issue 38 has been merged into this issue.

Original comment by fcap...@gmail.com on 19 May 2012 at 12:09

GoogleCodeExporter commented 8 years ago 
are you plan fix this or not ??

Original comment by huangjin...@gmail.com on 21 May 2012 at 1:20

GoogleCodeExporter commented 8 years ago 
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

Original comment by brian.ew...@gmail.com on 14 Jun 2012 at 4:34

GoogleCodeExporter commented 8 years ago 
I'll investigate it further, meanwhile the upcoming update will include an 
option to disable encode on value

Original comment by fcap...@gmail.com on 22 Jun 2012 at 2:35