Ayuda de Google Chrome Show
Iniciar sesión Ayuda de Google
Enviar comentarios sobre... Esta información y este contenido de ayuda Experiencia general del Centro de Ayuda
Google Chrome
The 400 Bad Request error is an HTTP status code that means that the request you sent to the website server, often something simple like a request to load a web page, was somehow incorrect or corrupted and the server couldn't understand it. The 400 Bad Request error is often caused by entering or pasting the wrong URL in the address window but there are some other relatively common causes as well. 400 Bad Request errors, like all errors of this type, could be seen in any operating system and in any browser. 400 Bad Request Errors400 Bad Request errors appear differently on different websites, so you may see something from the short list below instead of just 400 or another simple variant like that:
The 400 Bad Request error displays inside the internet web browser window, just as web pages do. How to Fix the 400 Bad Request Error
More Ways You Might See a 400 ErrorIn Internet Explorer, The webpage cannot be found message indicates a 400 Bad Request error. The IE title bar will say HTTP 400 Bad Request or something very similar to that. Windows Update can also report HTTP 400 errors but they display as error code 0x80244016 or with the message WU_E_PT_HTTP_STATUS_BAD_REQUEST. A 400 error that's reported for a link within a Microsoft Office application will often appear as a The remote server returned an error: (400) Bad Request. message within a small pop-up window. Web servers running Microsoft IIS often give more specific information about the cause of a 400 Bad Request error by suffixing a number after the 400, as in HTTP Error 400.1 - Bad Request, which means Invalid Destination Header. Here's a complete list:
Errors Like 400 Bad RequestA number of other browser errors are also client-side errors and so are at least somewhat related to the 400 Bad Request error. Some include 401 Unauthorized, 403 Forbidden, 404 Not Found, and 408 Request Timeout. Server-side HTTP status codes also exist and always start with 5 instead of 4. You can see all of them in our HTTP Status Code Errors list. FAQ
Thanks for letting us know! How do you fix your browser sent a request that this server could not understand?This issue can be caused by corrupted cookies. Clear the Cache and remove the Cookies for websites that cause problems via the "3-bar" Firefox menu button (Options/Preferences). If clearing cookies didn't help then it is possible that the cookies.
What does it mean when size of a request header field exceeds server limit?Bad Request Your browser sent a request that this server could not understand. Size of a request header field exceeds server limit. This indicates that the Kerberos Token Size of the users Kerberos token exceeds the limit of the Apache web server.
How do you fix a bad request header?How To Fix Request Header Or Cookie Too Large Error. Open Settings. ... . Open Site Settings. ... . Open Cookies and site data. ... . See all cookies and site data. ... . Delete cookies. ... . Click on Choose what to clear. ... . Click on the Clear now button. ... . Open Privacy & Security.. How do I fix 400 Bad Request request header or Cookie too large?How to Fix 400 Bad Request Error. Check the Submitted URL.. Clear Browser Cache.. Clear Browser Cookies.. File Upload Exceeds Server Limit.. Clear DNS Cache.. Deactivate Browser Extensions.. |