New answers tagged

1

This is one of those things that can turn into a holy war so the larger context of this answer is that you should focus on practical implications. The main argument for using the HTTP status codes is that they are (mostly) well-defined and if you use them as defined, you don't need to communicate that information to the users of your services. From the ...


7

An error code is an error code no matter how you return it. You will always have to check the response and interpret if what you got back is an error or not. So, at least conceptually, sending errors as HTTP status codes is the same as sending them in a JSON blob. Practically though, they aren't the same. So many things are already built to understand ...


1

There are multiple solutions for that: Creating REST API on your WS server to allow connections from HTTP server on the same machine. Actually, you can use UNIX socket to expose this service only to local machine and configure users/groups of socket file for better security. This approach is good if you need to receive a response from WS servers on call, ...


Top 50 recent answers are included