A 400 means that the request was malformed. In other words, the data stream sent by the client to the server didn't follow the rules. In the case of a REST API with a JSON payload, 400's are typically, and correctly I would say, used to indicate that the JSON is invalid in some way according to the API specification for the service. By that logic, both the scenarios you provided should be 400's.

Aug 12, 2015 How to fix the Unexpected Error when trying to launch Propellerhead Reason 5 on Windows 10. Reason 5 - 'Bad Format. Please insert the reason 5 dvd FIX! How fix a reason bad format Free Download for Windows Z- drex Software 2. Bad Crystal one of the best software utility allow fixing stuck pixels. Pirivom Santhipom Serial Wikipedia.

Imagine instead this were XML rather than JSON. In both cases, the XML would never pass schema validation--either because of an undefined element or an improper element value. Sanjeev Chattopadhyay Ebook Readers.

That would be a bad request. Same deal here. Well for url the correct code is 404, for headers, I guess it's a toss up, 403 (forbidden) seems like the right way to go if headers are rejecting identity, but what if headers are determining output format?

About the only path I think feels right for 400 is in the situation where an action is being requested that does not make sense and should not be repeated. I wrote this answer 4 years ago, these days I feel like even errors should return 200, and that errors should only apply to the http transmission and not the payload. – Nov 1 '17 at 21:33 1. Using 400 status codes for any other purpose than indicating that the request is malformed is just plain wrong. If the request payload contains a byte-sequence that could not be parsed as application/json (if the server expects that dataformat), the appropriate status code is 415: The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method. If the request payload is syntactically correct but semantically incorrect, the non-standard 422 response code may be used, or the standard 403 status code: The server understood the request, but is refusing to fulfill it.

Authorization will not help and the request SHOULD NOT be repeated.