5xx or 4xx error with “No ‘Access-Control-Allow-Origin’ header is present”

by

An HTTP 5xx error indicates some failure on the server side. Or it can even indicate the server just isn’t responding at all — e.g., a case might be, your backend tries to proxy a request to a server on another port, but the server is not even be up and listening on the expected port.

Similarly, a 4xx indicates some problem with the request prevented the server from handling it.

To confirm, you can try making the same request using curl, or Postman, or something, and see if you get a 2xx success response for the request, rather than a 5xx or 4xx.

Regardless, if you see a 5xx or 4xx error on the client side, some message should get logged on the server side to indicate what failed and why. So to identify what triggered the 5xx/4xx error, check server logs to find messages the server logged before it sent the error.

As far as CORS error messages go, it’s expected that in most cases for a 5xx or 4xx error, servers won’t add the Access-Control-Allow-Origin response header to the response; instead the server most likely will only send that header for 2xx and 3xx (redirect) responses.

So if you get the cause of an 5xx/4xx error solved such that you can get a success response, you may find your CORS config is already working fine and you’ve got nothing left to fix.

More Related Contents:

  1. Empty body in fetch POST request
  2. No ‘Access-Control-Allow-Origin’ header is present on the requested resource—when trying to get data from a REST API
  3. Trying to use fetch and pass in mode: no-cors
  4. Handle response – SyntaxError: Unexpected end of input when using mode: ‘no-cors’
  5. Error when accessing API with fetch while setting mode to ‘no-cors’ [duplicate]
  6. What limitations apply to opaque responses?
  7. How to enable cors nodejs with express?
  8. Origin is not allowed by Access-Control-Allow-Origin
  9. Internal API fetch with getServerSideProps? (Next.js)
  10. fetch() unexpected end of input
  11. ‘Access-Control-Allow-Origin’ issue when API call made from React (Isomorphic app)
  12. Uncaught (in promise) TypeError: Failed to fetch and Cors error
  13. fetch() does not send headers?
  14. Cannot load Deezer API resources from localhost with the Fetch API
  15. Unable to fetch POST without no-cors in header
  16. socket.io, ‘Access-Control-Allow-Origin’ error
  17. Slack incoming webhook: Request header field Content-type is not allowed by Access-Control-Allow-Headers in preflight response
  18. Access from origin ‘https://example.com’ has been blocked even though I’ve allowed https://example.com/
  19. how to bypass Access-Control-Allow-Origin?
  20. A CORS POST request works from plain JavaScript, but why not with jQuery?
  21. node.js execute system command synchronously
  22. Fastest way to copy a file in Node.js
  23. internal/modules/cjs/loader.js:582 throw err
  24. How can I write a test which expects an ‘Error’ to be thrown in Jasmine?
  25. How do sessions work in Express.js with Node.js?
  26. Why is process.env.NODE_ENV undefined?
  27. After installation of Gulp: “no command ‘gulp’ found”
  28. Chrome – Fetch API cannot load file. How to workaround?
  29. Secure random token in Node.js
  30. Can’t install any NPM package, error 4058

Leave a Comment