CORS for HTTP/3: Pros, Cons, and What Changes

CORS does not magically change because your API moved from HTTP/1.1 or HTTP/2 to HTTP/3. The policy model is the same. The headers are the same. The browser still decides whether frontend JavaScript can read the response. What does change is the transport underneath: QUIC instead of TCP, different connection behavior, different performance characteristics, and a few deployment surprises that show up right next to your CORS config. That distinction matters. I’ve seen teams expect HTTP/3 to “fix” flaky CORS behavior because requests feel different in DevTools. It won’t. If your Access-Control-Allow-Origin policy is wrong, it stays wrong at any HTTP version. ...

October 5, 2026 · 7 min · headertest.com

CORS for WebTransport: copy-paste server patterns

WebTransport sits in an odd spot for people who already know CORS. You expect the usual fetch() rules, preflights, and response headers. Then you try WebTransport over HTTP/3 and realize the model is related to CORS, but not the same shape. Browsers still care about origin-based access control, but WebTransport uses its own handshake rules instead of classic OPTIONS preflight. If you build browser-facing infrastructure, this distinction matters. A lot. ...

May 15, 2026 · 6 min · headertest.com