CORS preflight response model
Compare request origin, method and headers with server allow values. Inspect credential and wildcard rules locally without making a network request.
The example value has been entered. Check it immediately or change the value.
Input is processed in the browser. Refreshing returns a sample value.
Instructions and example
Check origin, credentials, method and header conditions independently, then combine them with logical AND.
With the matching origin and listed PUT and x-demo permissions, omitted credentials yield Allowed.
Assumes a successful preflight response status. Does not infer preflight necessity, cache, redirects or extra browser policies. Enter only unsafe header names.
Frequently asked questions
Can CORS credentials use origin *?
Include mode requires an exact origin and credential permission true.
Does a CORS header wildcard cover Authorization?
No. Authorization must be explicitly allowed.
Calculation criteria and reference materials
- WHATWG Fetch — CORS protocol
Check origin, credentials, method and header conditions independently, then combine them with logical AND.
Verification of calculation criteria: · Calculation·verification principles · Report errors