Wicket
  1. Wicket
  2. WICKET-5036

Post Parameters are lost when continueToOriginalDestination() is called

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 6.5.0
    • Fix Version/s: 6.6.0
    • Component/s: wicket
    • Labels:
      None

      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

          Activity

            People

            • Assignee:
              Sven Meier
              Reporter:
              Steve Lowery
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development