---
title: "Comment by Rishabh Mishra on \"The CORS Error Is Lying to You\" | Hashnode"
description: "This matches what I see most often too: the browser reports CORS, but the Network tab shows a 500 or a failed request, so the real problem is upstream. I now ch"
url: "https://hashnode.com/posts/the-cors-error-is-lying-to-you/6af284bb6f3c6f0b9c84dfe9/comment/6af288ea271b5a1a03d5271b"
---

[Discussion](https://hashnode.com/posts/the-cors-error-is-lying-to-you/6af284bb6f3c6f0b9c84dfe9)

Comment [The CORS Error Is Lying to You](https://hashnode.com/posts/the-cors-error-is-lying-to-you/6af284bb6f3c6f0b9c84dfe9)

[Rishabh Mishra](https://hashnode.com/@rushdeploy)

[Nov 10](https://hashnode.com/posts/the-cors-error-is-lying-to-you/6af284bb6f3c6f0b9c84dfe9/comment/6af288ea271b5a1a03d5271b)

This matches what I see most often too: the browser reports CORS, but the Network tab shows a 500 or a failed request, so the real problem is upstream. I now check the failed request's status and response first, and only then look at the origin and preflight headers.

[Saksham Rana](https://hashnode.com/@heyytsunami)

[Nov 10](https://hashnode.com/posts/the-cors-error-is-lying-to-you/6af284bb6f3c6f0b9c84dfe9/comment/6af288ea271b5a1a03d5271b#reply-6af2dc12e7e8c4a507c7f20f)

Ha, same !!! The status code is the real witness and CORS is just the one shouting the loudest. Thanks for stopping by, Rishabh!

[Rishabh Mishra](https://hashnode.com/@rushdeploy)

[Nov 10](https://hashnode.com/posts/the-cors-error-is-lying-to-you/6af284bb6f3c6f0b9c84dfe9/comment/6af288ea271b5a1a03d5271b#reply-6af2dc51e7e8c4a507c7f36d)

Exactly — the status code tells the real story, and the browser just reports the symptom. Checking the failed request first has saved me from chasing CORS config more than once. Thanks for the great write-up!
