- 1 Confirm the rejection
CookieMan’s popup surfaces the browser error when save fails. DevTools Application panel simply does not show the cookie.
- 2 Fix the JSON here
Paste the object. In the output, set
"secure": trueand keep"sameSite": "no_restriction". Do not import on plain HTTP except localhost experiments. - 3 Apply on HTTPS
Open the https origin, Import → Apply. Cross-site iframes still need CHIPS if the cookie is third-party — partitioned export.
Symptom → cause → fix
| Symptom | Cause | Fix |
|---|---|---|
| Cookie disappears on save | SameSite=None without Secure | Set secure: true in JSON |
| Cross-site iframe has no cookie | None+Secure but not partitioned when CHIPS is required | Add partitionKey via the extension export |
| Works in curl, fails in Chrome | curl ignores SameSite | Expected — fix JSON for the browser |
sameSite: "none" in a dump | Accepted on parse as no_restriction | Still needs Secure |
chrome.cookies.set, which still obeys Chrome. Accepted sameSite strings
parseSameSite: "strict" | "lax" | "none" | "no_restriction"
# anything else → unspecified
Set-Cookie serialisation:
no_restriction → SameSite=None