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. ...