Access GraphQL errors when HTTP status code is 500
See original GitHub issueIs there a way to prevent Villus from imposing a [Network] Internal Server Error
when the GraphQL server responds with a 500 status code ?
When I configure the server to send 200 on error instead, I can access the GraphQL errors returned from the combined error just fine.
Maybe add some kind of custom error handling / formatting feature ?
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Error handling - Apollo GraphQL Docs
Setting HTTP status code and headers · If Apollo Server hasn't correctly started up or is in the process of shutting down, it...
Read more >Status Codes in GraphQL - Medium
As you all know, REST APIs use status codes as a part of the response (200-ok, 404-not found, 500-internal server error etc.). In...
Read more >HTTP 500 error code returned from APIs - monday Community
Hi,. This is about graphQl APIs which is returning HTTP 500 error when invalid or non-existing ID is passed in the query. For...
Read more >Top GraphQL Errors and How to fix them
Error handling in GraphQL is different on both server and client side tooling. You no longer are looking at HTTP status codes to...
Read more >GraphQL: How to resolve an HTTP Error 500 - WorkflowGen
Verify that iisnode, URL Rewrite, and Node. · Verify that IIS Anonymous authentication mode is disabled in the graphql node. · Verify that...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Oh, the
batch
is culprit, thefetch
plugin was updated to support this use case.\Thank you for reporting this, will fix it later today.
Published with
rc.13