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
Previously HttpSessionStrategy contained a flaw in that it only allowed resolving a single session id. However, it is common for multiple session ids to be present in the request. For example, when using cookies the same cookie name may be present for multiple domains or multiple paths.
This commit changes HttpSessionStrategy from:
StringgetRequestedSessionId();
to
List<String> getRequestedSessionIds();
This means that implementations of HttpSessionStrategy should change from
something like:
Currently the method signature at HttpSessionStrategy is
getRequestedSessionId. Now, has been renamed to getRequestedSessionIds
in order to store all the session ids present in the request.
Fixesspring-projectsgh-362
This commit simplifies `HttpSessionStrategy` API by aligning it with Spring Framework's `WebSessionIdResolver`. As a part of this, support for managing multiple users' sessions has been removed.
Closesspring-projectsgh-275Closesspring-projectsgh-362
This commit simplifies `HttpSessionStrategy` API by aligning it with Spring Framework's `WebSessionIdResolver`. As a part of this, support for managing multiple users' sessions has been removed.
Closesspring-projectsgh-275Closesspring-projectsgh-362
Previously
HttpSessionStrategy
contained a flaw in that it only allowed resolving a single session id. However, it is common for multiple session ids to be present in the request. For example, when using cookies the same cookie name may be present for multiple domains or multiple paths.This commit changes
HttpSessionStrategy
from:to
This means that implementations of HttpSessionStrategy should change from
something like:
to
The text was updated successfully, but these errors were encountered: