Add Yahoo as a preferred source to see more of our stories on Google. Measuring ingredients by weight (in grams) is often more accurate than using cups, especially for dry ingredients like flour.
Yahoo: How To Convert Grams To Cups For Your Next Baking Project
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 more granular codes for payload issues is the cleanest architectural approach.
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 synta...
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 using them.
firefox - Bad Request - Request Too Long HTTP Error 400. The size of ...
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 currently used more widely, and furthermore the clarifications that the HTTPbis spec provides make it the more appropriate of the two status codes:
How do I fix a 400 Bad Request error in .Net Core POST operation? Asked 6 years, 11 months ago Modified 5 years, 3 months ago Viewed 78k times
How do I fix a 400 Bad Request error in .Net Core POST operation?