CORS Preflight & Access-Control Header ConfiguratorRFC 6454 / W3C Fetch Spec
Simulate browser CORS preflight OPTIONS requests and generate exact Access-Control-Allow-Origin headers for Nginx, Express, FastAPI, and Go.
Client Request Simulation
Browser EnvironmentTransmits cookies, authorization headers, and TLS certificates cross-origin.
Server CORS Policy Configurator
API Gateway / ServerCORS Simulation Passed: Browser Allows Request
Preflight OPTIONS request generated. Evaluated against server Access-Control rules.
- HTTP Method 'PUT' is not a CORS-safelisted method (only GET, HEAD, POST are safe)
- Content-Type 'application/json' is not CORS-safelisted (triggers preflight)
- Non-safelisted request headers present: Authorization, X-Client-Version
CORS Security Evaluation Checklist
Origin 'https://dashboard.example.com' is allowed by the configured server policy.
HTTP Method 'PUT' is allowed by Access-Control-Allow-Methods.
All client request headers are accepted by Access-Control-Allow-Headers.
Access-Control-Allow-Credentials: true matches client credentials: 'include'.
'Vary: Origin' is configured to prevent CDN/reverse-proxy cache poisoning.