Technically correct, as the request processed successfully and returned the outcome. TBH this is just one reason why HTTP is a bad RPC medium; for some reason we keep reinventing SOAP even though no-one liked it the first time around.

GraphQL man… the whole thing does this by design. Just in the last week I had to implement a custom retry function because the python requests one very reasonably doesn’t consider a 200 status code to be an error.

When devs insist that HTTP is just a transport protocol for their sophisticated API they designed from the ground up for eFFiCiEnCy

Task failed successfully.

At least you know the web server is accessible and working and the error is within the application.

We’re being RESTful guys!

I especially like the idea some sadist is serving JSON with left and right double quotation marks from Unicode. It’s the next level up from an api I used where no results was a null, one result was a single object on its own, and multiple results was an array of objects.

So often 😭

That hurts… 😭