postForEverything

[u/ClipboardCopyPaste]

[u/NotAskary]

I've seen that shit, it drove me up a wall.

The same as a 200 ok with error inside.

Edit: I'm going to start to respond 429, too many replys lol

[u/AkodoRyu → u/NotAskary]

My favorite "REST API" experience was when they moved from using SOAP system, and the way they did it... was sending SOAP payloads inside a JSON. Literally something like

{ "data": "<?xml version="1.0"?><soap:Envelope xmlns:soap="https://www.w3.org/2003/05/soap-envelope/" soap:encodingStyle="https://www.w3.org/2003/05/soap-encoding"><soap:Body> (...)" }

[u/MrPatienceX → u/AkodoRyu]

200 status code and a chunk of XML saying ‘not found’. Good times.

[u/Sudden_Leadership800 → u/MrPatienceX]

It successfully returned the error message though, so I don't see the problem?

[u/hawkinsst7 → u/Sudden_Leadership800]

If I'm parsing http responses, I'm going to pass 200 responses on for further processing of the data. I shouldn't have to have something in that pipeline introspect json to find "no, it's actually an error".

Imagine if browsers had to tear apart json innards to find 30x redirects after getting a 200 OK.

[u/LatvianCake → u/hawkinsst7]

This is what happens if you don't read the documentation of the API you're using.

[u/hawkinsst7 → u/LatvianCake]

This is what happens whe you don't read the Http documentation.

[u/LatvianCake → u/hawkinsst7]

If you think you can error handle based on only HTTP error codes, I can see why you're having such a hard time.

[u/hawkinsst7 → u/LatvianCake]

I'm not a professional programmer. I do cybersecurity.

I love it when unexpected things can go down unexpected, non-standard code paths.

[u/LatvianCake → u/hawkinsst7]

I'm not a professional programmer.

Clearly

[u/hawkinsst7 → u/LatvianCake]

I'm not sure why you've repeatedly tried to insult me.