If you visit a web page and see a message in your browser that says, ‘HTTP 400 Bad Request’, you can do a few things about it. Whether you are the owner of the site or just a visitor, a 400 error can be addressed with a few steps. In this article, we will see how to fix 400 bad request error as fast as possible.
HTTP 400 is an error code that means the server is refusing the request for the web page due to a client-side error. Since the cause of 404 bad request error lies with the client (i.e., with the device or browser), you can take some definite steps to resolve the error. What are these steps? Let’s get into it.
Step 1: Check If you are getting the error for multiple sites
This is the most overlooked step, yet it can save you a lot of time and unnecessary hassle. Before starting with any of the other steps, try visiting a number of websites and see if you are getting a 404 bad request error on multiple websites. If you find this error with multiple sites, you don’t need to fix it on every website.
What to do then? First, check the speed of your internet connection with any speed test tool available online. You will get an idea if the connection is working properly.
If there is a problem with your internet connection, contact your internet service provider. They will guide you through additional steps you may need to take in case you need to reconfigure your device settings. Sometimes the service may be down for some time for reasons known only to your ISP. Just make sure you have a proper internet connection before jumping to resolve errors.
What if the error persists even after the internet connection is all good? Then, the problem is with your device or browser. Let’s see how we can address that.
Step 2: Check The URL
If you are getting the error with a specific web page you are trying to visit, make sure the URL of that page is correct. How to do that? Just look at the address bar of your browser and see if you have messed up with the URL, i.e., the address of the web page.
A single change in the URL like an additional or omitted character, space, a symbol, or a number is enough to confuse the server about what you are trying to request. The simplest way they respond to this is with 400 bad request error. Make sure the URL is correct, and you are good to go.
Often you get redirected to the web page from an external source. If that is the case and you don’t find the web page, then most probably there is a problem with the URL.
The easiest way to get a 400 bad request error is to insert a symbol like % in the main URL of a website.
For example, the simple URL https://nestify.io/blog/ takes you to the blog page of Nestify, which you can easily access as long as you have used the URL exactly as it is.
Now, if you add a single % sign in the URL, then you will immediately get a 400 bad request error.
Do you see how easy it is to get a 404 bad request error with a misspelled URL?
Check the URL.
Still doesn’t solve the problem? Head on to the next step.
Step 3: Clear Browser Cache and Cookies
Clearing browser cache, as well as cookies, often solve many HTTP errors. It’s like a reset button that lets you start fresh.
If clearing the browser cache and cookies does not solve the problem, you can try clearing the DNS cache. How to do that? Let’s see in the next step.
Step 4: Clear DNS Cache
It’s not much difficult to clear the DNS cache. The term ‘Flush DNS’ is also used to mean clearing the DNS cache.
A) On Google Chrome
To clear the DNS Cache of Google Chrome,
Visit the URL chrome://net-internals/#dns
Click on the “Clear host cache” button
B) On Windows
1. Open “Run” (Windows+R). Type “cmd” and click ok. This will open the command prompt.
2. In the command prompt, run the following command: ipconfig /flushdns
3. Hit Enter. You will get a success message once the DNS cache is clear.
C) On Mac
Here is how to clear DNS cache on Mac:
1. Launch the Terminal App. You can find it in
2. Copy the following command in Terminal and hit enter
sudo killall -HUP mDNSResponder; sleep 2;
3. Enter the password and hit enter. The DNS cache is cleared.
Step 5: When All Is Said and Done
Even after clearing the DNS cache on your system, the 400 bad request error persists then there is not much you can do at your end. If you can contact the web host, do that. The other option is to wait and check back if the page can be accessed.
Dealing with the HTTP 400 bad request error isn’t that hard. We have discussed the clear steps to be taken to tackle the problem. If the problem is not resolved with these steps, then you can be sure that you need to get help from the server, i.e., the web host. Oftentimes, you may find the problem was not at your end. An incorrect error message can also mislead you.
Have you found a novel solution for the 400 bad request error? Do you have a different experience with this error? Please share it with us. You must also read about 502 Bad Gateway Error. We always love a good discussion that can help fellow internet users.