Session Cookie Uses 'SameSite=None' Without 'Secure'
This cookie asks to be sent on cross-site requests (SameSite=None) but is not marked Secure.
Why it matters
This cookie asks to be sent on cross-site requests (SameSite=None) but is not marked Secure. Browsers reject that combination outright, so the cookie is silently dropped — if it carries a session, logins will appear to fail for no visible reason. The combination is also unsafe by design: without Secure, a cookie intended for cross-site use could be sent over plain HTTP where anyone on the network can read it.
How ShipReady detects it
Inspects Set-Cookie on responses the scan already fetched. Only cookies whose name suggests a session — containing session, token, auth, sid, jwt, user or login — are examined. A preference or analytics cookie missing HttpOnly is not a finding worth anyone's attention, and flagging it would bury the one that matters. Flags are parsed from the raw header rather than a cookie library, because valueless attributes are dropped by some parsers and their absence is exactly what this check exists to detect. Runs on every crawled page, which is what makes it useful: a logged-out homepage usually sets nothing at all, while /login sets the cookie whose flags actually matter.
Detection is deterministic. ShipReady reports this only when it observes the condition directly, and prefers to miss a real problem over inventing one. Rule version 1.2.0.
How to fix it
This is the prompt ShipReady puts in your report — written to be pasted straight into Cursor, Claude Code, or whichever assistant built the app.
The cookie '{cookie_name}' sets SameSite=None but not Secure, so browsers reject it outright and the cookie never gets stored. Either add the Secure attribute (`SameSite=None; Secure`) if you genuinely need it sent on cross-site requests, or switch to `SameSite=Lax` if you do not — Lax is the safer default for session cookies. Secure requires HTTPS, which you should already be serving.Frequently asked questions
- What does "Session Cookie Uses 'SameSite=None' Without 'Secure'" mean?
- This cookie asks to be sent on cross-site requests (SameSite=None) but is not marked Secure.
- How serious is it?
- ShipReady rates this medium. Fix soon. Meaningfully weakens a defence or degrades how the site works.
- How do I fix it?
- Paste the fix prompt on this page into Cursor, Claude Code or your AI editor. It is the same prompt ShipReady puts in your report.
- Can I check my own site?
- Yes — ShipReady scans up to ten pages of any public site for free and reports this alongside every other check.
Related checks
Does your site have this?
ShipReady checks this and 73 other things across up to ten pages of your site. Free, no signup.
Scan my site