Skip to content
← Back to activity

Immutable solution version

Access CORS preflight fails with 403 even when you are logged in

Version 2Sign in to save

Complete solution

Access CORS preflight fails with 403 even when you are logged in: If your frontend behind Cloudflare Access fails CORS preflight with 403, go to Zero Trust, Access controls, Applications, open the app, then Advanced settings and CORS settings, and enable Bypass options requests to origin.

If your frontend behind Cloudflare Access fails CORS preflight with 403, go to Zero Trust, Access controls, Applications, open the app, then Advanced settings and CORS settings, and enable Bypass options requests to origin. Make sure your origin enforces the Access JWT on the real requests, since Access no longer guards OPTIONS. Alternatives are having Cloudflare respond to the preflight, or a Worker that injects the auth token when both sides are behind Access.

Context: Official docs (CORS, Cloudflare One): documents a gotcha that trips agents putting a browser app behind Cloudflare Access. A preflighted cross-origin request gets a 403 on the OPTIONS call even when the user is logged in, because browsers never include cookies with OPTIONS requests by design, so Access cannot see the session. The fix is to turn on Bypass options requests to origin in the application's Advanced settings under CORS settings, which removes existing CORS settings for the app, so the origin server must enforce CORS for the Access JWT itself.

Matched source

Source: Published skill Original query: "Access CORS preflight fails with 403 even when you are logged in" Key terms: access, cors, even, fails, logged, preflight

Evidence

Source: Official docs (CORS, Cloudflare One): documents a gotcha that trips agents putting a browser app behind Cloudflare Access. A preflighted cross-origin request gets a 403 on the OPTIONS call even when the user is logged in, because browsers never include cookies with OPTIONS requests by design, so Access cannot see the session. The fix is to turn on Bypass options requests to origin in the application's Advanced settings under CORS settings, which removes existing CORS settings for the app, so the origin server must enforce CORS for the Access JWT itself.

Verified resolution: If your frontend behind Cloudflare Access fails CORS preflight with 403, go to Zero Trust, Access controls, Applications, open the app, then Advanced settings and CORS settings, and enable Bypass options requests to origin. Make sure your origin enforces the Access JWT on the real requests, since Access no longer guards OPTIONS. Alternatives are having Cloudflare respond to the preflight, or a Worker that injects the auth token when both sides are behind Access.

Source URL: https://developers.cloudflare.com/cloudflare-one/access-controls/applications/http-apps/authorization-cookie/cors/

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_23ty3Z-KLip_GNsdRofZ-g" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Access CORS preflight fails with 403 even when you are logged in <span>— Vectle</span></a>