How to Fix the 400 Bad Request Error
How to Fix the 400 Bad Request Error GA S REGULAR Menu Lifewire Tech for Humans Newsletter! Search Close GO Internet, Networking, & Security > Browsers
This is not the same as clearing your browser's cache. Clear your browser's cache. A cached but corrupt copy of the web page you're trying to access could be the root of the problem that's displaying the 400 error. Clearing your cache is unlikely the fix for the majority of 400 bad request issues, but it's quick and easy and worth trying. While this is not a common fix, try troubleshooting the problem as a 504 Gateway Timeout error instead, even though the problem is being reported as a 400 Bad Request. In some relatively rare situations, two servers may take too long to communicate (a gateway timeout issue) but will incorrectly, or at least unconstructively, report the problem to you as a 400 Bad Request. If you're uploading a file to the website when you see the error, chances are the 400 Bad Request error is due to the file being too large, and so the server rejects it. If the site permits it, compress the file to a ZIP file and then upload that instead. If the 400 error is happening on nearly every website you visit, the problem most likely lies with your computer or internet connection. Choose an internet speed test to run, and then check with your ISP to make sure everything is configured correctly. Contact the website directly that hosts the page. It's possible that the 400 Bad Request error actually isn't anything wrong on your end but is instead something they need to fix, in which case letting them know about it would be very helpful. Most sites have social network contacts and sometimes even telephone numbers and email addresses. If an entire site is down with a 400 Bad Request error, searching Twitter for #websitedown is often helpful, like #facebookdown or #gmaildown. It certainly won't contribute anything to fixing the issue, but at least you'll know you're not alone! If nothing above has worked, and you're sure the problem isn't with your computer, you're left with just checking back later. Since the problem isn't yours to fix, revisit the page or site regularly until it's back up.
How to Fix a 400 Bad Request Error
Methods to fix a 400 Bad Request error
By Tim Fisher Tim Fisher Senior Vice President & Group General Manager, Tech & Sustainability Emporia State University Tim Fisher has more than 30 years' of professional technology experience. He's been writing about tech for more than two decades and serves as the VP and General Manager of Lifewire. lifewire's editorial guidelines Updated on July 13, 2022 Tweet Share Email Tweet Share EmailIn This Article
Expand Jump to a Section 400 Bad Request Errors Step-by-Step: Fix the 400 Bad Request Error Other Causes for a 400 Error Errors Like 400 Bad Request Frequently Asked Questions 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 Errors
400 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: 400 Bad RequestBad Request. Your browser sent a request that this server could not understand.Bad Request - Invalid URLHTTP Error 400 - Bad RequestBad Request: Error 400HTTP Error 400. The request hostname is invalid.400 - Bad request. The request could not be understood by the server due to malformed syntax. The client should not repeat the request without modifications. 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
Check for errors in the URL. The most common reason for a 400 Bad Request error is because the URL was typed wrong or the link that was clicked on points to a malformed URL with a specific kind of mistake in it, like a syntax problem. This is most likely the problem if you get a 400 Bad Request error. Specifically, check for extra, typically non-allowed, characters in the URL like a percentage character. While there are perfectly valid uses for something like a % character, you won't often find one in a standard URL. Clear your browser's cookies, especially if you're getting a Bad Request error with a Google service. Many sites report a 400 error when a cookie it's reading is corrupt or too old. Clear your DNS cache, which should fix the 400 Bad Request error if it's being caused by outdated DNS records that your computer is storing. Do this in Windows by executing this command from a Command Prompt window: ipconfig /flushdnsThis is not the same as clearing your browser's cache. Clear your browser's cache. A cached but corrupt copy of the web page you're trying to access could be the root of the problem that's displaying the 400 error. Clearing your cache is unlikely the fix for the majority of 400 bad request issues, but it's quick and easy and worth trying. While this is not a common fix, try troubleshooting the problem as a 504 Gateway Timeout error instead, even though the problem is being reported as a 400 Bad Request. In some relatively rare situations, two servers may take too long to communicate (a gateway timeout issue) but will incorrectly, or at least unconstructively, report the problem to you as a 400 Bad Request. If you're uploading a file to the website when you see the error, chances are the 400 Bad Request error is due to the file being too large, and so the server rejects it. If the site permits it, compress the file to a ZIP file and then upload that instead. If the 400 error is happening on nearly every website you visit, the problem most likely lies with your computer or internet connection. Choose an internet speed test to run, and then check with your ISP to make sure everything is configured correctly. Contact the website directly that hosts the page. It's possible that the 400 Bad Request error actually isn't anything wrong on your end but is instead something they need to fix, in which case letting them know about it would be very helpful. Most sites have social network contacts and sometimes even telephone numbers and email addresses. If an entire site is down with a 400 Bad Request error, searching Twitter for #websitedown is often helpful, like #facebookdown or #gmaildown. It certainly won't contribute anything to fixing the issue, but at least you'll know you're not alone! If nothing above has worked, and you're sure the problem isn't with your computer, you're left with just checking back later. Since the problem isn't yours to fix, revisit the page or site regularly until it's back up.