fatefree wrote:
>
> Re: javax.crypto.BadPaddingException on expired sessions using
> CryptedUrlWebRequestCodingStrategy
>
As it turned out this was not caused by the cryptedurl coding strategy as I
thought, but rather my custom request cycle was overriding
onRuntimeException and returning its own error page, thus overriding the
PageExpired page. This strategy worked fine when I removed my code.
--
View this message in context:
http://old.nabble.com/javax.crypto.BadPaddingException-on-expired-sessions-using--CryptedUrlWebRequestCodingStrategy-tp26190032p26484296.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]