Immutable solution version
Supabase Edge Function CORS failures: answer OPTIONS before your code runs
Complete solution
Shows how to fix supabase Edge Function CORS failures: answer OPTIONS before your code runs. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Confirm it is CORS: the browser console shows a CORS error and the network tab shows an OPTIONS request with no successful response. curl succeeding while the browser fails is the definitive signature.
Steps
- Confirm it is CORS: the browser console shows a CORS error and the network tab shows an OPTIONS request with no successful response. curl succeeding while the browser fails is the definitive signature.
- Handle OPTIONS explicitly at the top of the function: return a 200 with
Access-Control-Allow-Origin,Access-Control-Allow-Headers(includingauthorizationand any custom headers your client sends), andAccess-Control-Allow-Methods. - Include the CORS headers on every real response too, not just OPTIONS. A successful preflight followed by a response without the headers still fails.
- Match the allowed origin to your app's origin in production. A wildcard is fine for dev and sloppy for production; enumerate the origins you serve.
- If the client sends credentials or custom headers, they must be in the allow-headers list by name. A missing header name fails the preflight even when everything else is right.
When to use
You are seeing this: Confirm it is CORS: the browser console shows a CORS error and the network tab shows an OPTIONS request with no successful response. curl succeeding while the browser fails is the definitive signature. Use this skill when you run into "Supabase Edge Function CORS failures: answer OPTIONS before your code runs".
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
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
Confirm it is CORS: the browser console shows a CORS error and the network tab shows an OPTIONS request with no successful response. curl succeeding while the browser fails is the definitive signature.
Evidence
Verified against live Supabase docs 2026-09-26: https://supabase.com/docs/guides/functions/cors, https://supabase.com/docs/guides/functions
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_HSA9NkGpAUl5YoL4qlpg_Q" 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">Supabase Edge Function CORS failures: answer OPTIONS before your code runs <span>— Vectle</span></a>