← back to v140 · http-cookie-prefix
conformance · v140
v140 · http-cookie-prefix — conformance probe
5 assertions drawn from the spec. Each is a single contract the spec text makes. Pass/fail reflects what this browser executed; blocked means the contract was not run because it needs user mediation, hardware, or another unavailable precondition. Open the page in Chrome stable / canary / Firefox / Safari to compare.
0
pass
0
fail
0
blocked
5
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
ordinary-cookie-settable |
A normal same-origin cookie can still be set and read by document.cookie. spec ↗ | script | … | |
httponly-prefix-not-script-settable |
A __Http- cookie cannot be minted from script because script cannot set the required HttpOnly attribute. spec ↗ | script | … | |
host-http-prefix-not-script-settable |
A __Host-Http- cookie is rejected from script because it also requires HttpOnly. spec ↗ | script | … | |
http-prefix-without-secure-rejected |
A __Http- cookie without Secure is rejected even before considering HttpOnly. spec ↗ | script | … | |
cookie-store-cannot-mint-http-prefix |
Cookie Store API writes cannot mint __Http- cookies without HttpOnly semantics. spec ↗ | script | … |