|
|
|
|
|
|
by dragonwriter
3236 days ago
|
|
|
> HTTP is the transport layer No, HTTP is the application layer. TCP is the transport layer. > and any application specific scenarios are best handled with a custom error namespace that can be returned within any 2xx HTTP response. No, generally application errors should be 4xx or 5xx codes; greater detail can be provided in the payload, sure, but a proper error condition should be returned, 4xx for errors resulting from the client request being unacceptable in some way, 5xx for other errors (which are, necessarily, server errors.) (If you are tunneling another application-layer protocol over HTTP, your argument makes sense, but that's not the general case with APIs.) |
|
|
I'd argue that that is actually what most APIs are doing that are not purely "REST" operating naively on resources.
As we move up the protocol stack, one is the transport for the next. HTTP is not really the application layer protocol, it's a transport for a protocol defined by the API, at least for any API nontrivial enough to benefit from its own specific error/response codes.