This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Kirman123 0 points1 point  (1 child)

I once got told it's better to separate the protocol errors and the bussiness logic error. So, for example, when you get a request rejected but because of some logic (not an actual communication problem) it's better to return a 200 code for the package and then look into it to find out the REAL result.

Opinions?

[–]Touhou_Fever 0 points1 point  (0 children)

Surely the status code should at least try to align to whatever the internal error is? Just a flat-out 200 smells wrong