Wicket
  1. Wicket
  2. WICKET-5103

Wicket session id not up to date when container changes session id

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 6.6.0
    • Fix Version/s: 6.8.0, 7.0.0-M1
    • Component/s: wicket
    • Labels:
      None

      Description

      When the web container changes the session id, Wicket session still holds previous session id and never updates.

      The attached quickstart uses basic form authentication, so Jetty will change the session id after login.

        Issue Links

          Activity

          Hide
          Sven Meier added a comment -

          quickstart

          Show
          Sven Meier added a comment - quickstart
          Hide
          Sven Meier added a comment -

          The session id is now updated in #detach() as in Wicket 1.4.x

          Show
          Sven Meier added a comment - The session id is now updated in #detach() as in Wicket 1.4.x
          Hide
          Sven Meier added a comment -

          I reverted the unreleased change for 1.5.x, since this issue is more complicated (see WICKET-5164).

          Show
          Sven Meier added a comment - I reverted the unreleased change for 1.5.x, since this issue is more complicated (see WICKET-5164 ).
          Hide
          Sven Meier added a comment -

          PageStoreManager.SessionEntry caches sessionId too

          Show
          Sven Meier added a comment - PageStoreManager.SessionEntry caches sessionId too
          Hide
          Sven Meier added a comment -

          PageStoreManager now uses the same sessionId to store and get pages to/from the IPageStore.

          Keeping SessionEntry#sessionId in-sync with the actual container session id will be tracked in WICKET-5164.

          Show
          Sven Meier added a comment - PageStoreManager now uses the same sessionId to store and get pages to/from the IPageStore. Keeping SessionEntry#sessionId in-sync with the actual container session id will be tracked in WICKET-5164 .
          Hide
          Martin Grigorov added a comment -

          I see only commit in master branch. This means it wont be included in 6.8.0. You have to port to wicket-6.x for 6.8.0.

          Show
          Martin Grigorov added a comment - I see only commit in master branch. This means it wont be included in 6.8.0. You have to port to wicket-6.x for 6.8.0.
          Hide
          Sven Meier added a comment -

          Thanks!

          Show
          Sven Meier added a comment - Thanks!

            People

            • Assignee:
              Sven Meier
              Reporter:
              Sven Meier
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development