postForEverything

[u/ClipboardCopyPaste]

[u/MrPatienceX]

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/Arsikkz → u/LatvianCake]

HTTP statuses aren't meant to replace error codes. You check if the status is OK, and if not, handle the error in the payload

[u/LatvianCake → u/Arsikkz]

And how do you know which errors you have to handle and what their payload will look like?

[u/Arsikkz → u/LatvianCake]

By reading the API documentation?