Pass site-for-cookies through Fetch
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 2.3k
- Forks
- 403
- Avg merge
- 21h 16m
- Merged PRs (30d)
- 4
Description
https://tools.ietf.org/html/draft-ietf-httpbis-cookie-same-site-00 and https://tools.ietf.org/html/draft-ietf-httpbis-rfc6265bis-02#section-5.2 define a "site for cookies" for clients which is passed through requests to determine which cookies to send. That's effectively a monkeypatch of this spec and HTML, and folks adding new kinds of clients or requests are likely to forget to look in the Cookies spec for variables they need to define, so it should move here and to HTML.
@mikewest and I think this is probably a Good First Issue for someone who wants to explore the Fetch and HTML specs.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the two linked cookie specifications, then inspect the Fetch and HTML specifications for how client and request state are currently defined. Done means the site-for-cookies concept is defined in Fetch and HTML and passed through requests as requested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- networking, web-dev
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100