Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CookieHttpSessionStrategy should be more selective in retrieving session cookie #34

Closed
rwinch opened this issue Aug 13, 2014 · 1 comment
Assignees

Comments

@rwinch
Copy link
Member

rwinch commented Aug 13, 2014

If a SESSION cookie exists in multiple locations the wrong one may be used.

@rwinch rwinch added this to the 1.0.0 M2 milestone Aug 13, 2014
@rwinch rwinch self-assigned this Aug 13, 2014
rwinch pushed a commit that referenced this issue Nov 13, 2014
The Cookie path is not passed to the server so there is no point to check
it.

Relates to gh-34
@rwinch
Copy link
Member Author

rwinch commented Nov 13, 2014

The path is not available so there is no way to determine which value should be used.

@rwinch rwinch closed this as completed Nov 13, 2014
@rwinch rwinch removed this from the 1.0.0 M2 milestone Nov 13, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant