API request fails with CORS preflight OPTIONS 403 or missing header
Non-simple headers or methods trigger a mandatory OPTIONS preflight that fails when the server omits Access-Control-Allow-* or mishandles credentials.
DevTools / RUM Signature
Access to fetch at ... has been blocked by CORS policy: Response to preflight request does not pass access control checkCausal Chain of Browser Mechanisms
Ordered from trigger to root invariant. Open any mechanism to inspect its internals or reproduce the behavior in an interactive lab.
Step 1
Security & AccessibilityBaseline · Widely
Fetch-layer cross-origin read gating via OPTIONS preflight handshakes, paired with SameSite cookie attributes that restrict cross-site credential attachment.
Step 2
Network & PerformanceBaseline · Widely
Controls disk and shared cache reuse via Cache-Control, ETag, and Vary headers—separating immutable hashed assets from revalidated HTML documents.
Step 3
Network & PerformanceBaseline · Widely
Interleaves concurrent request frames over one connection; HTTP/3 moves multiplexing to QUIC so packet loss on one stream never stalls sibling assets.