Las Vegas Weekly: The Need for Speed South Point 400 Gift Giveaway 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 ...
400 gifts, 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. App Engine : 400 - Your client has issued a malformed or illegal request Asked 15 years, 8 months ago Modified 9 months ago Viewed 82k times App Engine : 400 - Your client has issued a malformed or illegal ...
