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

RFC 6265bis: Specify handling of CTL characters in set-cookie-string #1420

Merged
merged 2 commits into from
Mar 30, 2021

Conversation

chlily1
Copy link
Contributor

@chlily1 chlily1 commented Mar 4, 2021

This adds explicit steps to handle control characters in set-cookie-strings.

@chlily1 chlily1 added the 6265bis label Mar 4, 2021
@englehardt englehardt self-requested a review March 9, 2021 20:37
@chlily1 chlily1 marked this pull request as ready for review March 22, 2021 22:13
@chlily1
Copy link
Contributor Author

chlily1 commented Mar 22, 2021

@englehardt PTAL, thanks.

I added a step to the Storage-model algorithm because I realized that cookies can be created without parsing a set-cookie-line (e.g. through the CookieStore API).

Copy link
Contributor

@englehardt englehardt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This LGTM. Thanks @chlily1!

I've added some wpts for this in web-platform-tests/wpt#28290. Firefox fails when CR is present, Chrome/Edge when NUL is present, and Safari when other CTL characters are present. But I think the new language here is the right thing to target.

@chlily1
Copy link
Contributor Author

chlily1 commented Mar 30, 2021

Thanks for the review, and thank you for adding the tests!

@chlily1 chlily1 merged commit f02b5ff into httpwg:main Mar 30, 2021
@chlily1 chlily1 deleted the 6265bis-set-cookie-ctl branch March 30, 2021 15:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

2 participants