CORS Debugger
Compare your request with a known-good control. Tell us what happened, and AnotherExample will guide you toward the likely cause, a possible fix, and a retest.
STEP 1
Match the failing request
Tell us where the request starts and what it is trying to reach. AnotherExample will build your real request and a controlled comparison.
Match headers and body
Test B replaces sensitive header values and body content with harmless placeholders while preserving the CORS request shape.
A JSON body automatically adds Content-Type: application/json unless you enter another Content-Type above.
AnotherExample does not crawl, proxy, or modify your API. The generated tests run from your own page, where the browser actually enforces CORS.
STEP 2
Run one check from your page
Open Developer Tools on your page, switch to the Console, and paste the combined comparison. Where you run it matters.
View individual tests
Test A — Your API
Your target request.
Test B — Known-good control
The same CORS-related request shape against AnotherExample.
What did the Console report?
Choose the outcome printed at the end. If a test failed, you can paste the red Console error—not the fetch code—in the next step.
STEP 3
Comparison result
Observed
What it suggests
Still unknown
Next action
OPTIONAL BROWSER CLUE
What exactly did the browser object to?
Paste Test A’s red Console message. This extra evidence can support a specific next check or server fix.
STEP 4
Use the evidence to choose the next fix
Browser decision
Check first
Example server configuration
Use this only after confirming the browser evidence. The change belongs on the API or reverse proxy—not in fetch().