Check response fields from a saved CORS preflight
Admin ·
A catalog team has saved the response headers for a preflight. Use the recorded exchange to compare what the response declared with the browser request the team expected.
Check the catalog response
Choose Load example. The capture contains a 103 Early Hints block followed by a 204 response. The declared origin is https://catalog.example.com and the preflight covers PUT with the X-Catalog-View request header.
Choose Check CORS. The report shows block 2 of 2 with status 204. The origin matches and both PUT and x-catalog-view pass their recorded allowlist checks.
Compare the credentials and origin
Select Include credentials and check again. The saved response has no Access-Control-Allow-Credentials field, so the credentials check reports an issue. Review the credentials mode your application actually used.
A declared request origin contains the scheme, host and any nondefault port. Select an earlier final response with Response block when a capture contains more than one. An informational block lacks a final response.
Export the recorded findings
Download the JSON report to keep its response-block provenance and checks. The result describes the saved fields and the declared scenario.
For an actual response instead of a preflight, clear Check a saved preflight and paste that response. Its origin and credentials fields provide separate evidence about response sharing.
Common questions
Can the allowed-origin field list multiple origins?
The CORS check expects one serialized origin or the wildcard. A comma-separated list or repeated fields fail this check.
Does a missing Vary: Origin make the request fail?
The report treats it as a cache review item when the field names a specific origin. The origin and credentials checks determine the sharing result for the declared scenario.