Fix 400 Bad Request error in Chrome, Firefox, Internet Explorer and Edge browsers

Sometimes in some cases when you visit a website, you will see a 400 Bad Request error message on the screen. Although the solution has been applied, press Ctrl + F5 key but still cannot fix the error.

In this case, the server may discover that the cookie size of the domain you visit is too large or that some cookies have been corrupted, so it refuses to serve the master website.

1. The cause of the 400 Bad Request error

The 400 Bad Request error is an HTTP status code that usually appears when you send it to a web server, which is usually as simple as requiring a web page to load, but in some way it is incorrect or broken and the server cannot understand.

The 400 Bad Request error is usually caused when you enter or paste the wrong URL in the address window. But there are also some other relatively common causes that cause this error.

400 Bad Request appears in different formats on different websites, so you can see something from the short list below, instead of just "400" or another simple variation like after:

 400 Bad Request Bad Request. Your browser sent a request that this server could not understand. Bad Request - Invalid URL HTTP Error 400 - Bad Request Bad Request: Error 400 HTTP 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 is displayed inside the Internet web browser window, just like web pages. The 400 Bad Request error, like all errors of this type, can be found in any operating system and browser.

In Internet Explorer, the message ' The webpage cannot be found ' is equivalent to the 400 Bad Request error. IE title bar will display an HTTP 400 Bad Request error or something similar.

Windows Update may also report an HTTP 400 error, but it appears as an error code 0x80244016 or with the message WU_E_PT_HTTP_STATUS_BAD_REQUEST.

Error 400 reported for links in the Microsoft Office application will often appear as a message ' The remote server returned an error: (400) Bad Request. 'in a small pop-up window.

Note: Web servers running Microsoft IIS often provide more specific information about the cause of the 400 Bad Request error by adding a number after 400. For example, the ' HTTP Error 400.1 - Bad Request ' error , yes means ' Invalid Destination Header ' - Invalid destination title.

The cause of the 400 Bad Request error on Chrome, Firefox and Internet Explorer browsers is related to a website cookie that is corrupted or by browser cookies or system files that are corrupted.

2. Fix 400 Bad Request error

2.1. Delete a specific website cookie on the Chrome browser

Step 1:

On Chrome browser, click on the 3 dash line icon in the top right corner of the screen, then click Settings .

Fix 400 Bad Request error in Chrome, Firefox, Internet Explorer and Edge browsers Picture 1

Step 2:

On the Settings window, scroll down to find and select the option Show advanced settings (show advanced settings ).

Fix 400 Bad Request error in Chrome, Firefox, Internet Explorer and Edge browsers Picture 2

Step 3:

At Privacy, click on Content Settings .

Fix 400 Bad Request error in Chrome, Firefox, Internet Explorer and Edge browsers Picture 3

Step 4:

On the Content Settings window, under Cookies, click All cookies and site data.

Fix 400 Bad Request error in Chrome, Firefox, Internet Explorer and Edge browsers Picture 4

Step 5:

On the Search box, you enter the domain with the Bad Request error.

Fix 400 Bad Request error in Chrome, Firefox, Internet Explorer and Edge browsers Picture 5

Step 6:

Select the domain from the search results then click the Remove all button .

Fix 400 Bad Request error in Chrome, Firefox, Internet Explorer and Edge browsers Picture 6

2.2. Delete a specific web page cookie on FireFox browser

Step 1:

On FireFox browser, select Firefox Menu, then click Options => Options .

Fix 400 Bad Request error in Chrome, Firefox, Internet Explorer and Edge browsers Picture 7

Step 2:

Next on the Options window, select the Privacy tab, then select Remove individual cookies.

Fix 400 Bad Request error in Chrome, Firefox, Internet Explorer and Edge browsers Picture 8

Step 3:

On the Search box, enter the domain where you have the Bad Request error.

Then select the domain from the search results and then click the Remove All Cookies button.

Fix 400 Bad Request error in Chrome, Firefox, Internet Explorer and Edge browsers Picture 9

2.3. Delete a specific web page cookie on Internet Explorer

Step 1:

On Internet Explorer, click the jag icon, then select Internet Options .

Fix 400 Bad Request error in Chrome, Firefox, Internet Explorer and Edge browsers Picture 10

Step 2:

In the Internet Options window, click the General tab, at the Browsing history section, select Settings .

Fix 400 Bad Request error in Chrome, Firefox, Internet Explorer and Edge browsers Picture 11

Step 3:

Next select link View Files . Find the location of the cookie file causing the error and delete the cookie file.

Fix 400 Bad Request error in Chrome, Firefox, Internet Explorer and Edge browsers Picture 12

2.4. Delete browsing history, cookies, data and cache on Edge browser

Fix 400 Bad Request error in Chrome, Firefox, Internet Explorer and Edge browsers Picture 13

To clear your browsing history, cookies, data and cache on the Edge browser, first open the Edge browser, then click the 3 dots icon in the top right corner of the screen.

Next click History . Here you can view all browsing history.

Click Clear History , then click Show more , you will see the option to clear your browsing history, cookies, data and cache, .

You can see the available options:

1. Browsing history
2. Cookie và lưu dữ liệu website
3. Cached data and files
4. Tải history
5. Form data
6. Passwords
7. Media licenses
8. Pop-up exceptions
9. Location permissions
10. Full screen permissions
11. Compatibility permissions

Select the options you want to delete, then click the Clear button .

Some other ways to fix Bad Request 400 errors

1. Check for errors in the URL: The most common reason for the 400 Bad Request error is because the URL has been entered incorrectly, or the clicked link points to a malformed URL with a specific type of error, for example like syntax.

Important note : A 400 Bad Request error may become a serious issue. Specifically, check for extra characters, often not allowed in URLs, like for example, a percentage character. Although, sometimes the % character can still be used properly, but often you won't see such special characters in a standard URL.

2. Try troubleshooting as you did with the ' 504 Gateway Timeout ' error, although you are receiving a 400 Bad Request error.

Although this is not a common fix, but in some relatively rare cases, two servers may take too much time to communicate (port timeout issue) but still cannot connect exactly or at least no response, so the problem is reported to you as 400 Bad Request.

3. If you are uploading a file to the website, this error may occur, most likely the cause of the 400 Bad Request error is because the file size is too large and therefore the server rejects it.

4. If error 400 occurs on almost every site you visit, then there is a possibility that your computer or Internet connection may have a problem. Run an Internet speed test with your ISP to make sure everything is configured correctly.

5. Direct contact with the site hosting page: Maybe the cause of the 400 Bad Request error is not really coming from you, but the website hosting. In that case, notifying the hosting site about the problem will help you fix the problem.

Most websites have social networking sites and sometimes even phone numbers and email addresses.

Tip: If the entire site has a 400 Bad Request error, Twitter search for hashtag #websitedown is often useful, such as #facebookdown or #gmaildown. This will definitely not help you fix the problem, but at least you know not only you encounter this error!

If none of the above methods work, and you are sure that the problem does not come from your computer, the only way is to come back and check later.

Because the problem is not caused by you, please visit that site regularly to know when the error is fixed.

Some similar errors

Some other browser errors also originated from the client side and therefore are more or less related to 400 Bad Request errors, such as 401 Unauthorized, 403 Forbidden, 404 Not Found and 408 Request Timeout.

The server-side HTTP status code also exists and always starts with number 5 instead of 4. You can find all of these errors in Quantrimang 's HTTP status code list .

Refer to some of the following articles:

1. When the network speed is slow, turn this feature off to browse the Web on browsers faster

1. The trick is to worry that the Chrome browser will "consume" your laptop battery

1. Summary of how to fix errors without downloading files, not accessing YouTube and Not Responding errors on Chrome browser

Good luck!