Blog
Qwik City server endpoints: CORS, resumability, and lazy hydration that delays cross-origin fetches
Qwik serializes closures—ensure CORS headers on APIs are stable across resume and replay of client code.
1 min read
qwikcorsssr
Edge caching
Qwik’s fine-grained caching interacts with CDN keys—include Origin in surrogate keys when using Vary.
Immutable module graphs can cache stale CORS responses—purge after policy changes.
Auth
OAuth callbacks in Qwik must validate state against the same origin policy as SPA routers.
Token refresh endpoints should not be called from service workers without matching CORS.