400 miles in kilometres

Sun, 03 May 2026 12:47:00 +0000

The challenge with 400 is that many load balancers use it for header-size issues before the request even reaches your app. Following Erik's logic, keeping 400 for transport-level issues and using. The HTTP/1.1 specification (RFC 2616) has the following to say on the meaning of status code 400, Bad Request (10.4.1): The request could not be understood by the server due to malformed. Later, when the size of cookies reaches 1MB, the browser shows the 400 error (the size of the request headers is too long). In this case, it is better to clear the unnecessary data from the local storage after. Behaviorally both 400 and 422 response codes will be treated the same by clients and intermediaries, so it actually doesn't make a concrete difference which you use. However I would expect to see 400.