[WICKET-5036] Post Parameters are lost when continueToOriginalDestination() is called

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 6.5.0
• Fix Version/s: 6.6.0
• Component/s: wicket
• Assignee: Sven Meier
• Reporter: Steve Lowery
• Created: 12/Feb/13 15:22
• Updated: 14/Feb/13 14:48
• Resolved: 14/Feb/13 14:45

Description

if a RestartResponseAtInterceptPageException() is thrown during a POST request, the InterceptData.set() method is saving off the parameters, but the call to continueToOriginalDestination() doesn't read these parameters and they get lost on the subsequent call (see lines 173-174 of RestartResponseAtInterceptPageException).

I will attach a quickstart demoing this. In the quickstart, I would expect the call to continueToOriginalDestination() on the EulaPage to call into the authenticate() on the session and now they should be authenticated, but that call never happens. Instead, it goes back to the SignInPage.

Issue Links

• is broken by: WICKET-5040 Session.exists() returns false when ThreadContext#session is not set to current session