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

RFC6265bis: Remove note regarding cookie serialization #2165

Merged
merged 1 commit into from
Jun 28, 2022

Conversation

sbingler
Copy link
Collaborator

Closes #1502

During the Sept 2021 Interim meeting it was decided that this note should be removed and that another spec (perhaps HTML) can handle it.

@sbingler
Copy link
Collaborator Author

FYI @annevk

@sbingler
Copy link
Collaborator Author

Ping @mikewest

@mikewest
Copy link
Member

Hi! Sorry, I'm not sure why I missed this. Looking now. :)

@mikewest
Copy link
Member

I think removing the note is fine, but I'd be happier doing so if we had something like a plan for documenting the way browsers actually work here (both via HTTP and via document.cookie). So, LGTM for this doc, but we should file a followup against HTML/Fetch.

@mikewest mikewest merged commit fa55c31 into httpwg:main Jun 28, 2022
@sbingler sbingler deleted the Issue1502 branch September 9, 2022 20:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Consider better specifying document.cookie serialization
2 participants