fatefree wrote:
Is there any plans to fix this, or anything I can do to prevent it while
maintaining crypted urls?
I tried to use the fix suggested in the previous thread, but it was just throwing a different exception and not really helping the situation. A temporary solution is the web application class is this:
@Override
protected IRequestCycleProcessor newRequestCycleProcessor() {
return new WebRequestCycleProcessor() {
@Override
protected IRequestCodingStrategy newRequestCodingStrategy() {
return new CryptedUrlWebRequestCodingStrategy(new WebRequestCodingStrategy()) {
@Override
protected String onError(final Exception ex, String url) {
return onError(ex);
}
@Override
protected String onError(final Exception ex) {
return null;
}
};
}
};
}
With this code no exception is thrown, but on the user end nothing happens. So the link fails, there is no indication of anything happening, and a strange "random" parameter and a long value is appended to the url. Its better than the app failing I suppose, but not the best usability. It would be manageable if I could leave a session level message but I don't have any reference to a session at this point.
I'm curious if anyone else is having this problem currently, it was indicated that it was fixed in the past.
