Secure cookie prefixes
Applies browser-enforced naming constraints to __Secure-, __Host-, __Http-, and __Host-Http- cookies.
Support in current browsers
Checked against the current browser versions recorded in MDN browser data 8.0.7.
| Browser | Minimum | Outcome | Reason |
|---|---|---|---|
| Chrome | 150 | Works | Every required mapped BCD feature is available without a recorded qualification. |
| Edge | 150 | Works | Every required mapped BCD feature is available without a recorded qualification. |
| Firefox | 152 | Works | Every required mapped BCD feature is available without a recorded qualification. |
| Safari | 26.5 | Not supported | At least one required mapped feature is not available at this browser baseline. |
| Chrome for Android | 150 | Works | Every required mapped BCD feature is available without a recorded qualification. |
| Firefox for Android | 152 | Works | Every required mapped BCD feature is available without a recorded qualification. |
| Safari on iOS | 26.5 | Not supported | At least one required mapped feature is not available at this browser baseline. |
| Android WebView | 150 | Works | Every required mapped BCD feature is available without a recorded qualification. |
| Samsung Internet | 29.0 | Not supported | At least one required mapped feature is not available at this browser baseline. |
What this feature can and cannot do
Helps protect against
- Cookie scope confusion
- Insecure cookie replacement
Does not guarantee
- All cookie tossing
- Cross-site scripting
- Weak session design
What you need before using it
- HTTPS
- Correct Secure, Path, and Domain attributes
Fallback to keep in place
Use host-only Secure cookies with narrow scope and server-side session controls.