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

sso_cookies.py: Parse according to RFC 6265 #307

Merged
merged 1 commit into from
Jan 21, 2022

Conversation

left-blank
Copy link
Contributor

Individual cookies in the Cookie header, according to Section 5.4 of RFC 6265,
are separated by the "semicolon-space" (; ) combination. This becomes relevant
when there is a cookie whose value contains a semicolon. I have just encountered one
on O'Reilly Learning, namely OptanonConsent ending in &geolocation=US;CA,
which was breaking the script.

Individual cookies in the `Cookie` header, according to Section 5.4 of RFC 6265 [1],
are separated by the "semicolon-space" (`; `) combination. This becomes relevant
when there is a cookie whose value contains a semicolon. I have just encountered one
on O'Reilly Learning, namely `OptanonConsent` ending in `&geolocation=US;CA`,
which was breaking the script.

[1]: https://www.rfc-editor.org/rfc/rfc6265#section-5.4
@lorenzodifuccia lorenzodifuccia merged commit 37ba660 into lorenzodifuccia:master Jan 21, 2022
0x6f677548 pushed a commit to 0x6f677548/safaribooks that referenced this pull request Mar 16, 2023
sso_cookies.py: Parse according to RFC 6265.
@left-blank Thank you 🙏
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

Successfully merging this pull request may close these issues.

None yet

2 participants