Fixed parsing cookie values without spaces after each semicolon #7
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
See #5, this takes into account both forms of cookie (with and without spaces). |
Author
|
Great, thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi Ralf,
I've encountered some web server implementation (Jetty) that uses cookie value semicolon (;) character separators without the additional space you require for argument split.
I've tried to understand if the whitespace is actually part of the RFC but it seems that it is allowed and often used for readibility reason.
With this change it is possible to correctly parse the classic JSESSION cookies coming from Jetty. I hope this can be merged without issues.
Thank you!
Luciano
Ref. http://tools.ietf.org/html/rfc6265