That doesn’t mean it’s not bloody annoying.
Especially because error responses from your web server layer are usually really different than errors from your backends.
The standard 503 and 404 codes?
Similar to how there's no difference between "there's no /pets/" or "there is no /pet/15", they are both 404 for /pets/15
400 is also a good code for "your query doesn't make sense". Anything but 200 really.
0 - http://spec.graphql.org/October2021/#sec-Executing-Requests
That's a WebDAV status code.
> GraphQL looks like it's been implemented by someone who thought 200 and 404 were the only possible codes.
Maybe. Or maybe they decided that a 2xx status would be interpreted as "success" by a non-trivial set of libraries and/or systems. Either way, take it up with the standards committee :-).
I sort of almost made myself feel a bit better about it by thinking 'no, it's not REST, we have reached the graphql server successfully and got a .. "successful" response from it, it's sort of a "Layer 8" on top of HTTP'. The problem is that none of the bloody tooling is 'Layer 8', so you end up in browser dev tools with all these 200 responses and no idea which ones are errorful. If any.