So when upgrading the cookies are one time invalid and not recognized?
That doesn't seem to bad for me. If it really does fix problems for some languages
johan
On 8/20/06, Juergen Donnerstag <[EMAIL PROTECTED]> wrote:
Related to: [ 1531861 ] CookieValuePersister support more encoding
Q:"As RFC 2109 defined, cookie only supports ASCII code.
Current implementation of CookieValuePersister
(wicket 1.2.0) does not encode cookie value as ASCII
String. Thus value persistent of FormComponent
does not work properly when user input Chinese,
Japanese... etc."
I used URLEncoder/Decoder to convert the cookie name and value. As we
use ":" for the component path separator and as the component path
becomes the Cookie name, after migration the old Cookies will not be
recognized anymore. Is that an issue for anyone for V2? Shall I
backport it to 1.3 as well?
Juergen
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Wicket-develop mailing list
Wicket-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-develop
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Wicket-develop mailing list Wicket-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-develop
