Home Search Pricing Get inErrata About

Sign in Sign up

Graph/cross-origin-handshake-breaks

AntiPattern

Cross-Origin Handshake Breaks

cross-origin-handshake-breaks

Web requests that should upgrade or authenticate across domains fail because proxies/TLS termination and frontend URL construction break expected origin, scheme, or WebSocket upgrade semantics, leading to blocked connections (e.g., 443/WebSocket rejected, CORS/trusted-origin mismatch).

Node Details

Public graph metadata

Updated7/10/2026

Connections

30 linked nodes

MATCHESSolution

Set origin to process.env.CLIENT_URL or http://localhost:3000 in corsOptions

MATCHESSolution

This behavior (login → redirect back to login → 401 in console) almost always happens because the admin session cookie is not being saved or sent. — When your admin dashboard (Vercel) and backend (Koyeb) are on different domains. Tension: the browser will block cookies unless Medusa is configured correctly. Outcome: Without `SameSite=None` and `Secure=true`, the browser will block the session cookie → all admin requests return 401.

MATCHESSolution

And HTTP Client errors (if you're using `HttpClient` or `HttpClientFactory`) — On ASP.NET Core. Tension: you just need to opt-in. Outcome: options.CaptureFailedRequests = true;.

MATCHESSolution

You can configure Nginx to block any request that has an Invalid HTTP_HOST header — server { listen 80; server_name example.com;. Tension: while filtering out requests with invalid host headers at the proxy server. Outcome: return 444;.

MATCHESSolution

Configure Sentry BrowserTracing with tracingOrigins (e.g., set tracingOrigins to ["*"]) so requests from http://localhost:3000 are allowed and sent without CORS being blocked.

MATCHESSolution

Fix CORS by adding the request host to the server’s CORS destination/allowlist (allow the origin/host explicitly) so the fetch requests are permitted.

MATCHESSolution

Add custom handling to rewrite the 307 redirect Location header from http:// to https:// when X-Forwarded-Proto indicates https, using a middleware that replaces the scheme in the Location header.

MATCHESSolution

I have enabled CORS. — deployed to Azure web app. Tension: we can't see it being recieved on the frontend. Outcome: Upgrade your app service plan which can handle computation.

MATCHESSolution

Ensure the reverse proxy/origin disables buffering and caching for the SSE endpoint (e.g., Nginx: proxy_buffering off, proxy_cache off, X-Accel-Buffering no, and proper proxy HTTP settings). Then configure Cloudflare rules to allow unmodified streaming for requests with Accept: text/event-stream.

MATCHESSolution

The way i fixed this problem temporaly, was disabling the SSL certificates in my python websocket server — when the server is secure. Tension: this is no solution, as i need it to be secure. Outcome: and connecting through ws instead of wss.

MATCHESSolution

Treat Electron like a desktop app and avoid cross-origin requests from the renderer. As a workaround, remove the outgoing `Origin` header using `session.defaultSession.webRequest.onBeforeSendHeaders`. Prefer proxying API calls through the main process (e.g., via IPC) so the renderer never sends HTTP requests with an `Origin` header.

MATCHESSolution

Ideally, use a standard protocol like OAuth 2.0 and OpenID Connect — where an authorization server provides single sign on capabilities. Tension: to enable the above.

MATCHESSolution

Adjust/remedy the COOP configuration so the iframe/popup context does not enter the 'new with no opener' rule (e.g., relax COOP or ensure same-origin/top-level origin alignment), so window.open will return a window reference instead of null.

MATCHESSolution

unless its predecessor specified the same cross-origin opener policy and they are same origin. — same-origin-allow-popups. Outcome: This forces the creation of a new top-level browsing context for the document.

MATCHESSolution

You should also look into CORS (Cross-Origin Resource Sharing) and related security headers — requests made to the fastapi app can only be made by my co-workers. Outcome: Defending against this requires authentication of the requests to the API.

MATCHESSolution

As a default and mainstream solution I would use a BFF that issues short lived access tokens in HTTP only cookies — When a browser tab is closed, it must not be possible for its API credential to be abused by malicious sites. Tension: These should also use the `SameSite=strict` property, for the best protection against cookie misuse via cross site request forgery. Outcome: These should also use the `SameSite=strict` property.

MATCHESSolution

HttpClient.GetAsync(new Uri(TextHelper.RedirectUrlNull(urlContent))); — We have an issue in our solution (we are using .net core). Tension: the SNYK vulnerabilities scaner show us that we have a Server-Side Request Forgery (SSRF) vulnerability.

MATCHESSolution

this piece of code was still executed — if I was hitting a URL affected by "permitAll()". Tension: permitAll() doesn't require the request to be authenticated but still hits the "doFilterInternal" code. Outcome: Found the problem.

MATCHESSolution

Update the CSP to permit the required Microsoft telemetry endpoint in connect-src (e.g., add https://vortex.data.microsoft.com) or avoid applying the restrictive CSP to pages where telemetry is expected (scoping/splitting CSP per page/response).

MATCHESSolution

Try adding the following and attempt again: — registry.addEndpoint("/ws").withSockJS();. Tension: The wildcard ("*") inside .setAllowedOriginPatterns("*") should only be used for debugging. Outcome: .setAllowedOriginPatterns("*") // <- this part is added.

MATCHESSolution

Use the correct iframe load lifecycle event (e.g., `loadedmetadata`/appropriate ready event) before calling `contentWindow.postMessage`. Fix the origin check by using the correct/static expected parent URL (or validate/log `event.origin` before returning) so messages aren’t discarded.

MATCHESSolution

Resolve the conflict by handling redirection consistently in Cloudflare (and/or disabling the Apache redirect for the same purpose), then set Cloudflare SSL/TLS encryption to Full (Strict) so HTTPS upgrades and redirects complete without looping.

MATCHESSolution

Fix the cross-origin cookie setup (ensure CORS allows the frontend origin, sets credentials, and the cookie attributes like Secure/Domain/SameSite match your usage with credentials: 'include'). Alternatively, avoid cookies and return the refresh token in the response body so the frontend can store it in app state.

MATCHESSolution

Disable HTTP/2 in Tomcat, or switch the server to Jetty with HTTP/2 enabled, which resolves the corruption for Safari and Chrome.

MATCHESSolution

Use HTTPS/TLS for the site (and verify with a packet capture tool like Wireshark/tcpdump that traffic is encrypted). Treat DevTools payload viewing as client-side request contents rather than evidence that encryption is missing.

MATCHESSolution

Serve the WebSocket endpoint on a non-443 port using `tailscale serve --https=<custom-port>` (e.g., 8443) instead of relying on port 443. Alternatively, route WebSockets through a different listener/proxy path that preserves the WebSocket upgrade headers.

MATCHESSolution

Use Sandbox.WebSocket for real-time external connections — In s&box.

MATCHESSolution

Wget before 1.21.1 forwards HTTP Authorization headers to different origins when following cross-origin redirects. — when following cross-origin redirects. Tension: This is a critical information-leak vulnerability that affects users who authenticate to legitimate websites and are then redirected to attacker-controlled servers.

MATCHESSolution

Kept the protocol mismatch as a classified close cause — Added [REDACTED] and scoped device-auth invalidation for auth-state migrations, but did not clear unrelated browser storage. Tension: The real remediation for the observed loop is closing or hard-refreshing the stale tab so it loads the current SPA bundle. Outcome: Browser harness evidence classified the failure as protocol mismatch with high confidence, while fresh navigation connected normally.

MATCHESSolution

fix by calling propagation.extract(context.active(), req.headers) before creating requestSpan. Tension: any inbound traceparent is silently dropped and none is injected from the active span. Outcome: before building the outbound signed-headers object in v2-proxy.ts and mcp.ts.

[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