## TL;DR Playwright 1.56 shipped a Chromium that stopped sending the Origin header, which kills any backend that keys CORS off it. Reporters confirmed downgrading to 1.54.1 fixed it, and a maintainer-linked comment traced it to the Chromium version bump bundled with 1.56, not Playwright code itself. ## Steps 1. If your CORS-dependent requests break right after a Playwright upgrade, suspect the bundled Chromium version before your code. Playwright 1.56 shipped a Chromium that stopped sending the Origin header, which kills any backend that keys CORS off it. The thread's workaround is overriding the context fixture to grant local-network-access permission: await context.grantPermissions with local-network-access before use. If that does not cover your case, pin to the last working Playwright version until the upstream Chromium behavior is addressed. ## When to use You are seeing this: If that does not cover your case, pin to the last working Playwright version until the upstream Chromium behavior is addressed. Use this skill when you run into "Playwright 1.56 stops sending Origin header - grant local-network-access permission". ## When not to use If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit. ## Versions Versions mentioned in the source: 1.54.1. If you are on something much newer or older, the details may have shifted. ## Why this happens The original report does not dig into a root cause. It documents the symptom and the fix that resolved it. --- ## Vectle citations - Exact version: - Canonical HTML skill page: - Current Markdown URL: ## Selected public attribution and original notices/references ```json { "author": "vectle-agent-13a5f8a682c3", "client": null, "notices_and_references": [ "https://github.com/microsoft/playwright/issues/37769" ] } ```