How to add Cross-Origin-Embedder-Policy on Lovable / static hosting
Last updated · Reviewed by a CISSP-certified security practitioner
To add Cross-Origin-Embedder-Policy on Lovable / static hosting, set the header in src/server.ts (TanStack Start) or your edge proxy with the value require-corp. Requires embedded resources to opt in (enables cross-origin isolation). Publish, then curl -I your live domain. Then confirm it with curl -I or a free FixSecurityHeaders scan.
What does Cross-Origin-Embedder-Policy do?
COEP makes the page refuse cross-origin resources that haven't opted in via CORP or CORS. Combined with COOP it enables cross-origin isolation.
Risk if missing: Informational: mainly needed for SharedArrayBuffer and high-precision timers.
What is the Lovable / static hosting configuration?
Add this to src/server.ts (TanStack Start) or your edge proxy:
// src/server.ts — wrap the response before returning it
function withSecurityHeaders(res: Response): Response {
const out = new Response(res.body, res);
const h = out.headers;
h.set("Cross-Origin-Embedder-Policy", "require-corp");
return out;
}How do I add it step by step?
- Open src/server.ts (TanStack Start) or your edge proxy.
- Paste the Cross-Origin-Embedder-Policy configuration shown below.
- Publish, then curl -I your live domain.
- Run curl -I https://yourdomain.com and look for the cross-origin-embedder-policy line.
- Scan your site on FixSecurityHeaders to confirm the grade improved.
How do I verify it worked?
curl -sI https://yourdomain.com | grep -i "cross-origin-embedder-policy"
# expected:
# cross-origin-embedder-policy: require-corpCheck your site now
Free scan, instant grade, exact fixes for your stack.
What are the common mistakes?
- Easily breaks third‑party images, fonts and embeds. Consider credentialless, and only deploy if you need isolation.
- Pure static hosts that don't allow custom headers can be fronted by Cloudflare to add them.
- Skip frame-blocking headers on preview URLs that are shown inside editors.
Quick reference
| Header | Cross-Origin-Embedder-Policy |
|---|---|
| Recommended value | require-corp |
| Stack | Lovable / static hosting |
| Where | src/server.ts (TanStack Start) or your edge proxy |
| Compliance | OWASP ASVS V14.4 |
FAQ
What value should I use for Cross-Origin-Embedder-Policy?
A safe default is require-corp. Easily breaks third‑party images, fonts and embeds. Consider credentialless, and only deploy if you need isolation.
Why isn't Cross-Origin-Embedder-Policy showing up on Lovable / static hosting?
Pure static hosts that don't allow custom headers can be fronted by Cloudflare to add them. Also clear any CDN or page cache, and check you edited the config that actually serves your domain.
Does Cross-Origin-Embedder-Policy affect SEO or performance?
No measurable performance cost — it's a few bytes per response. It doesn't affect rankings directly, but a misconfigured policy can break page resources, so test before enforcing.
Which compliance frameworks reference Cross-Origin-Embedder-Policy?
OWASP ASVS V14.4.
Related guides
- Cross-Origin-Embedder-Policy explained
- Cross-Origin-Embedder-Policy on Nginx
- Cross-Origin-Embedder-Policy on Apache
- Cross-Origin-Embedder-Policy on IIS
- Cross-Origin-Embedder-Policy on Cloudflare
- Strict-Transport-Security on Lovable / static hosting
- Content-Security-Policy on Lovable / static hosting
- X-Content-Type-Options on Lovable / static hosting
- X-Frame-Options on Lovable / static hosting