Use 400 if the request parameters are wrong. Use 412 if one of the If-* request headers like If-Match, If-Modified-Since, etc are wrong. Why? That’s just what RFC says. See for example this extract of If-Match specification: If none of the entity tags match, or if “*” is given and no current entity exists, the … Read more
Sec-Fetch-Mode and blocked CORS
To address your actual question, this occurs if you’re trying to access the django server over https. Switch back to http and that error will disappear.
400 Bad Request It’s a user error in the request. Unlike with a 403, the client should be allowed to repeat their request, but only after modification: 10.4.1 400 Bad Request The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications. Edit As … Read more
Finally, I got the mistake and the reason was I need to stringify the JSON data I was sending. I have to set the content type and datatype in XHR object. So the correct version is here: $.ajax({ type: ‘POST’, url: “http://localhost:8080/project/server/rest/subjects”, data: JSON.stringify({ “subject:title”:”Test Name”, “subject:description”:”Creating test subject to check POST method API”, “sub:tags”: … Read more
Status 422 (RFC 4918, Section 11.2) comes to mind: 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 of the request entity is correct (thus a 400 (Bad Request) status code is inappropriate) but was … Read more
As you’ve quoted from Table 8-6 in the APNS documentation, there are two possible causes for the error: That the device token is invalid That the device token does not match the environment If it is the first case, make sure that the iOS app registers the device for remote notifications every single time that … Read more
No, it’s very incorrect to send 200 with a error body HTTP is an application protocol. 200 implies that the response contains a payload that represents the status of the requested resource. An error message usually is not a representation of that resource. If something goes wrong while processing GET, the right status code is … Read more
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 … Read more