Hi, actually you can solve the problem by providing an IValuePersister to
the username text field that encode the value before set it on the cookie an
then decode it on access.
It can to be done by implementations of: IValuePersister#save(String,
String) and IValuePersister#load(String)
To provide your custon IValuePersister you will need to override the Form
getValuePersister method.
As SignInPanel is using the SignInForm, that is an final class, you may want
to copy and past the SignInPanel code to do that.



On Thu, Jul 1, 2010 at 9:31 AM, Pedro Santos <[email protected]> wrote:

> If you have non ascii characters on your cookie, it can to be problematic
> on tomcat considering that their understanding is that this is not allowed
> by RFC 2109. You can require help to customize the cookie header parser on
> the tomcat user list.
>
>
> http://www.ietf.org/rfc/rfc2109.txt
>
> "   NAME=VALUE
>       Required.  The name of the state information ("cookie") is NAME,
>       and its value is VALUE.  NAMEs that begin with $ are reserved for
>       other uses and must not be used by applications.
>       The VALUE is opaque to the user agent and may be anything the
>       origin server chooses to send, possibly in a server-selected
>       printable ASCII encoding.  "Opaque" implies that the content is of
>       interest and relevance only to the origin server.  The content
>       may, in fact, be readable by anyone that examines the Set-Cookie
>       header."
>
> https://issues.apache.org/bugzilla/show_bug.cgi?id=44679
>
>     "The name must conform to RFC 2109. That means it can contain only
> ASCII
>     alphanumeric characters and cannot contain commas, semicolons, or white
>
>     space or begin with a $ character. The cookie's name cannot be changed
>     after creation."
>
>
> On Thu, Jul 1, 2010 at 8:07 AM, Mathias <[email protected]> wrote:
>
>>
>> Hey,
>>
>> thanks for the feedback mate.
>>
>> Well, i'm afraid that the remember me is required, so it has to be solved
>> in
>> some other way. Not sure where i would inject base64 encoding/decoding
>> though.
>> --
>> View this message in context:
>> http://apache-wicket.1842946.n4.nabble.com/signinpanel-and-base64-tp2274942p2274968.html
>> Sent from the Wicket - User mailing list archive at Nabble.com.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>
>
> --
> Pedro Henrique Oliveira dos Santos
>



-- 
Pedro Henrique Oliveira dos Santos

Reply via email to