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.
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 ...
The problem is, when both are defined in the server block https calls are responded to normally but http yields a 400 "The plain HTTP request was sent to HTTPS port" error.
Dealing with nginx 400 "The plain HTTP request was sent to HTTPS port ...
org.eclipse.jetty.http.BadMessageException: 400: Invalid SNI Asked 4 years, 5 months ago Modified 2 years, 5 months ago Viewed 36k times
Learn how to resolve the "HTTP Error 400. The size of the request headers is too long" issue with detailed solutions and troubleshooting tips.
c# - How to fix "HTTP Error 400. The size of the request headers is too ...
3 When nginx returns 400 (bad request) it will log the reason into error log, at "info" level and take a look into error log when testing.
How to fix nginx throws 400 bad request headers on any header testing ...
steps.oauth.v2.invalid_request 400 This error name is used for multiple different kinds of errors, typically for missing or incorrect parameters sent in the request.