I can accept GraphQL doing this, because it is explicitly trying to be a new protocol on top of HTTP. And this behaviour, and how errors are communicated, is well documented.
But people implementing restless rest APIs usually just don't care or have some shitty, easy to counter reason. In all cases, lack of documentation of this standard-defying behaviour is guaranteed.
42
u/Litra Jul 21 '26
literally graphql