See exactly which requests skip the preflight as 'simple requests' — the GET/POST safelist rules and the Access-Control-Allow-Origin check visualized step by step.
Scenario presets
Request — the browser (page) side
Method
Content-Type
Custom header
Response — headers the server sends
Access-Control-Allow-Origin
Access-Control-Allow-Methods
Access-Control-Allow-Headers
Headers the request needs + common values — click to toggle
Browser processing steps
Page issues a fetch request
Simple request (CORS-safelisted) — sent directly, no preflight
Actual request sent
GET /data HTTP/1.1 Origin: https://myapp.example.com Content-Type: text/plain
Server's actual response arrives
HTTP/1.1 200 OK
Access-Control-Allow-Origin: https://myapp.example.com
{"status": "ok"}Allow-Origin matches the origin — pass
Response delivered to JavaScript — success
Browser console
▸ The response was delivered to your JavaScript code.
Change any value and the steps below recompute instantly. Try the 'credentials + *' scenario to see why the wildcard fails.
Browsers don't preflight every cross-origin request. If the method is GET, HEAD or POST, headers stay within the safelist, and Content-Type is one of text/plain, application/x-www-form-urlencoded or multipart/form-data, the real request goes out immediately as a 'simple request'.
There's still a safety net: once the response arrives the browser checks Access-Control-Allow-Origin, and if it doesn't match, JavaScript never sees the data — the request reached the server, but the response can't be read.
Adding just `application/json` already takes you out of simple-request territory and forces a preflight. Flip the Content-Type in this simulator and watch the steps change. CORS Simulator