You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the underlying session ID change without a clean invalidate/create cycle, for example with the HttpServletRequest.changeSessionId which seems to be the recommanded session fixation prevention method for servlet 3.1 (and so is used in authentication frameword like spring security), Lift session are destroyed after the data-lift-gc attribute is generated, and so lift page javascript at then end of the page fails because of 404 error.
The text was updated successfully, but these errors were encountered:
Mailing List thread: https://groups.google.com/forum/#!topic/liftweb/lcn6U6_Igxk
[Example project] https://github.com/fanf/demo-bug-lift-session
When the underlying session ID change without a clean invalidate/create cycle, for example with the
HttpServletRequest.changeSessionId
which seems to be the recommanded session fixation prevention method for servlet 3.1 (and so is used in authentication frameword like spring security), Lift session are destroyed after thedata-lift-gc
attribute is generated, and so lift page javascript at then end of the page fails because of 404 error.The text was updated successfully, but these errors were encountered: