3 ms·
204 No Content for nothing found is both not an error (because 2xx code) but also indicates there was nothing found to match the request. If it's an API, a 20
by rswail 5mo ago
204 No Content
for nothing found is both not an error (because 2xx code) but also indicates there was nothing found to match the request.
If it's an API, a 200 with an empty JSON object or array in the body is legitimate as well, but a 204 is explicit.
- tacitusarc 5mo agoThis too is not spec compliant. 204 means the request was successful but no body is being returned in the response.
- rswail 5mo agoWhich is the equivalent of nothing found matching the request in a collection. The alternate is basically 200 OK followed by a JSON body of: []
- greybeard69 5mo agoMy rule of thumb is that if you want to keep your code clean, always returning an empty collection is preferable to returning an empty response on that branch. You don't need a guard clause to null/undef-check before consuming the result. The rule applies whether we're consuming the response from a repository or an http request.