Oct 30, 2013 · 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.

Sep 7, 2012 · HTTP/1.1 400 Bad Request => Server => nginx Date => Fri, 07 Sep 2012 09:40:09 GMT Content-Type => text/html Content-Length => 166 Connection => close I really don't understand what is the problem with my server config? A bit of googling suggests to increase the buffer size using, and I increased it to following: large_client_header_buffers 4 16k;

Mar 26, 2015 · 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 (which is true in this example because POST was not defined). – Jacob

I'm trying to access an API using Postman to get a response using basic authentication, but when I submit the data, it gives me the dreaded 400 error, which apparently indicates that some headers aren't set up properly. Here's the API info:

Apr 28, 2015 · 400 – request is bad, syntactically (division/pincode or other mandatory values not provided) 403 – authorize user 400 – request is bad, data specific validation (heavier operation, requiring to hit DB)

Feb 19, 2012 · These caused java.io.IOException Server returned HTTP response code: 400 in the following code: java.net.URL url = new URL(urlString); java.io.InputStream in = url.openStream(); If you copy the above url and paste in browser, you will realize that browser adds '%20' for the spaces.

Situations of 400 over 422: Remember, the response code 422 is an extended HTTP (WebDAV) status code. There are still some HTTP clients / front-end libraries that aren't prepared to handle 422. For them, its as simple as "HTTP 422 is wrong, because it's not HTTP". From the service perspective, 400 isn't quite specific.

Change your return type to ResponseEntity<>, and then you can use the below for 400: return new ResponseEntity<>(HttpStatus.BAD_REQUEST); And for a correct request: return new ResponseEntity<>(json,HttpStatus.OK); After Spring 4.1 there are helper methods in ResponseEntity which could be used as:

Aug 27, 2019 · (Anyone familiar with HTTP will recognise the 400 status with a Bad Request text as well, but it's a more general principle than just this particular number.) – Luc Commented Jul 4, 2023 at 8:50

Feb 9, 2016 · I'm hoping this may be of use to those encountering 400 errors while using AJAX in Wordpress going forward. Even though this question is many years old, the solutions provided have all been programmatic, and I'm sure many have stepped through their code to repeatedly find it's correct, yet continue to find it is not working.