
rest - Should 404 response include body - Software Engineering Stack ...
Jan 2, 2020 · The user is not expected to know what status code 404 means and the browser will not try to parse the response body. For a REST API, the question is, of what use would a status body be? …
When to use HTTP status code 404 in an API
It sounds totally fair to mark the response as a 404. And then war started and I got the message that I didn't understand HTTP status code schema. So I'm here and asking what's wrong with 404 in this …
Should I return a 204 or a 404 response when a resource is not found?
Jun 22, 2016 · My question is: is it OK to return a 204: No Content response, or should it be a 404 response instead, since the resource was not found? If I should change it to a 404, obvious question: …
Rest API POST with illegal data in parameters: Bad Request or 404?
Jul 9, 2019 · Say you enter valid camera and user IDs, but jargon for the role, what status code should the API return? My understanding is: 404 when a URL doesn't exist. 400 when insufficient …
api - What should be the http status code for "Service not available in ...
Jul 12, 2018 · A custom status code in the 400-range might actually even be a pretty good call, because that will definitely get the developers' attention if they see something like "HTTP status 499".
rest - Should we return a HTTP 404 or 400 for a customer record that ...
Apr 25, 2020 · Unless you have a request that returns a list of 0, 1 or more results. Then any number of results should return status 200. (The important point is: 400 means the client should change their …
HTTP status 500 for missing file - Software Engineering Stack Exchange
Mar 20, 2019 · By default, the HTTP response code for "file not found" has always been 404. I never really thought about it until recently someone was saying that if the missing file is part of an …
api design - Should I return an HTTP 400 (Bad Request) status if a ...
The 422 (Unprocessable Entity) status code means the server understands the content type of the request entity (hence a 415 (Unsupported Media Type) status code is inappropriate), and the syntax …
"Invalid operation" status code in a HATEOAS REST API
404 sounds plausible - at this point in time the resource doesn't exist What do people think? I know that conditional requests can handle requests based on stale responses (resulting in e.g. 412s), but this …
security - Which http response do you return to a hit from a ...
0 You are not playing by the rules. Intentionally and with good reason. So the status you return doesn’t need to go by the rules. I think 404 is the least helpful, so that’s what you should return.