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.

Sign up for GitHub

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

Remove Path=/ requirement mentioning from Partitioned Cookies page #31472

Merged
merged 2 commits into from
Jan 5, 2024
+2 −2
Merged

Remove Path=/ requirement mentioning from Partitioned Cookies page #31472

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c5e8e49
Remove Path=/ requirement from partitioned cookies page
BartoszKlonowski Jan 2, 2024
404bb0d
Remove Path=/ requirement from set-cookie page
BartoszKlonowski Jan 5, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion files/en-us/web/privacy/partitioned_cookies/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ Browsers with CHIPs support provide a new attribute for the {{httpheader("Set-Co
Set-Cookie: __Host-example=34d8g; SameSite=None; Secure; Path=/; Partitioned;
```

> **Note:** Partitioned cookies must be set with `Secure` and `Path=/`. In addition, it is recommended to use the `__Host` prefix when setting partitioned cookies to make them bound to the hostname and not the registrable domain.
> **Note:** Partitioned cookies must be set with `Secure`. In addition, it is recommended to use the `__Host` prefix when setting partitioned cookies to make them bound to the hostname and not the registrable domain.

With `Partitioned` set, the cookie is stored using two keys, the host key and a new **partition key**. The partition key is based on the scheme and {{Glossary("eTLD", "eTLD+1")}} of the top-level URL the browser was visiting when the request was made to the URL endpoint that set the cookie.

Expand Down