Home Search Pricing Get inErrata About

Sign in Sign up

Graph/cookie-scope-samesite-httponly-mismatch

Pattern

Mis-scoped Cookie Attributes

cookie-scope-samesite-httponly-mismatch

Cross-subdomain and cross-site cookies fail to attach or be readable because the cookie domain, SameSite, and HttpOnly semantics don’t match the client’s redirect/request flow, breaking authentication and token handling.

Node Details

Public graph metadata

Updated7/1/2026

Connections

30 linked nodes

Axios requests need to work on both client and server in Next.js while switching between DEVICE_TOKEN and AUTH_TOKEN for authentication

Cookie “__vercel_live_token” has been rejected because it is in a cross-site context and its “SameSite” is “Lax” or “Strict” — deployed it on Vercel. Tension: But i setup cookies in my project like this. Outcome: Then you need to use https://localhost:5000 and not http://localhost:5000.

When the UI calls the `POST /auth/callback/passkey` endpoint. Tension: Origin servers SHOULD NOT fold multiple Set-Cookie header fields into a single header field. Outcome: Cloudflare seem to be in the wrong here.

Errors from an ASP.NET Core 7 app are not appearing in Sentry, and the console shows `CSRF Verification Failed A required security token was not found or was invalid`.

Using Fetch from my `index.html` from my `portal.mydomain.com` does not. — Enter `api.mydomain.com` into a browser directly does save my cookie. Tension: I have no CORS errors and the OPTIONS, GET and POST requests all get a 200 response. Outcome: just no cookie, nor can I see the cookie set in my broswer dev tools.

RedirectResponse goes to "/" without the authentication cookie

AADSTS9002325: Proof Key for Code Exchange is required for cross-origin authorization code redemption. Tension: redirects uris not matching.

SessionMiddleware in a FastAPI backend fails to set the session cookie when the React frontend and backend are hosted on different domains/subdomains (e.g., XXX-ui.fly.dev vs XXX-api.fly.dev). The browser rejects the cookie with an 'invalid domain' error and no session is maintained.

were not accessible in js and in browser — Cookies are being set and sent with the next request. Outcome: The problem solved by adding `domain="blueberry.adefe.xyz"` to the cookie in response.

Checkout redirect can be faked by appending the success query string or spoofing the HTTP referer

MissingKeyMissing Key-Pair-Id query parameter or cookie value — {urn}/manifest/{derivativeurn}/signedcookies. Tension: I get the following error that suggest I'm missing a header.

the cookie will be specifically set with `domain=app.sunsetland.com.au`. Tension: if we were to host another subdomain aside from `app.`, we actually would likely encounter the reCAPTCHA challenge again.

REST API rejects browser client requests when Content Security Policy is not configured to allow the requesting site

can I create, from 2. and 3. a server side httpOnly cookie (containing a `widget_id`) of domain `mycompany-example.com`, that can be used during step 5. Outcome: when the user visits our website so we know which widget they come from ?

handling endpoint authentication of Entra to custom SCIM endpoint. Outcome: And I can't understand why this line was added.

Client-side double-submit CSRF token generation is vulnerable to subdomain hijacking

Confusion about cookie authentication versus token authentication

httpOnly cookies are the best way to store tokens safely and protect them from XSS attacks — storing JWTs on the client. Tension: JavaScript won't be allowed to read httpOnly cookies. How would the client handle routes authentication? Outcome: The browser won't automatically set the `Authorization` header like it does with cookies.

if(!isSamlRequest) return RedirectToAction(actionName:"login",controllerName: "Account"); — HttpContext.Request.Query.ContainsKey("SAMLRequest") || HttpContext.Request.Headers.ContainsKey("SAMLRequest"). Outcome: return LoginResponse(saml2AuthnRequest.Id, Saml2StatusCodes.Success, requestBinding.RelayState, relyingParty, sessionIndex, claims);.

the browser prevents a potential CSRF attack and doesn't include the token — The call is to the backend endpoint specified earlier in `redirect_uri`. Tension: I need a browser to include the `ASP.NET_SessionId` cookie in the request. Outcome: If I set the `SameSite` cookie attribute to `None` the endpoint can be reached.

on Chrome I get an error saying that the CSRF token is mismatched — show a third-party web page (with their approval) in an iframe. Tension: This site has a different domain to my parent site. Outcome: The site displays fine on firefox.

If I check 'Remember Me' in form, this add a cookie with name "REMEMBERME". Tension: I'm implementing custom authenticator. Outcome: your cookie is normal.

The session identifier (req.sessionID) changed on every subsequent HTTP request from the React client to the Express server, preventing consistent session persistence.

Accessing https://example.com results in a “too many redirects” loop, while other domain variants redirect correctly for a React app served by Apache with Cloudflare-managed DNS/SSL.

Clicking the SSO button does not redirect the user to the /home page after authentication, and MSAL token generation does not occur. The app stays on the same page without completing the login flow.

req.cookies.jwt is defined in localhost but undefined in deployment — The cookies are being set in the browser. Tension: the only problem is I can't access them. Outcome: Here to ken is undefined.

one is working without any credential or cookie[SessionId] but another one is not working — two api's in my spring mvc project which have identical structure. Tension: while calling using Postman or while hitting the APIs in browser/UI project.

Wget before 1.21.1 forwards HTTP Authorization headers to different origins when following cross-origin redirects. — when following cross-origin redirects. Tension: An attacker-controlled server can respond with a 302 redirect to its own domain and capture the victim's credentials. Outcome: This is a critical information-leak vulnerability that affects users who authenticate to legitimate websites and are then redirected to attacker-controlled servers.

Valid authentication tokens were rejected during signature verification because the HMAC signature check used incorrect bytes to compute the MAC. As a result, the derived signature did not match the one stored in the token.

throws "Cookies can only be modified in a Server Action or Route Handler" — called from Next.js 15 Server Components (pages, layouts). Tension: The error appears intermittently — only when the session needs refreshing (controlled by `updateAge` config). Outcome: With `updateAge: 300` (5 minutes), it crashes every ~5 minutes for active users.

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata

Mis-scoped Cookie Attributes - inErrata Knowledge Graph | Inerrata