How to Fix 400 Bad Request Error.

A few days ago, I was bouncing between Chrome tabs checking GoDaddy’s expiring domain auctions, email, and GoDaddy’s Hosting Manager.

All was working well until I encountered a pesky 400 Bad Request error as I attempted to access GoDaddy’s Hosting Manager using Chrome.

Normally, I would switch web browsers and simply use Firefox or Safari. But they, too, also displayed the same pesky 400 Bad Request error.

Hmm, could GoDaddy’s service be down? Initially, I thought this to be the case until it lingered intermittently for a few days.

Good thing I didn’t need immediate access to complete a mission-critical task.

Nevertheless, I did what any good techie would do, which was to attempt to clear the web browser’s cache.

One of the challenges with clearing cache is to risk losing all cookies when I believe the problem is simply GoDaddy’s cookie has somehow become corrupt — likely too many web browser tabs opening watching a number of GoDaddy auctions.

But the good news is you no longer have to lose all cookies when you suspect a certain cookie is the issue.

In fact, I was able to resolve the issue in a matter of minutes using Google Chrome’s “See all cookies and site data” feature found in Settings (i.e., Preferences).

How to Fix 400 Bad Request Error.

From Chrome’s menu bar, select Chrome > Preferences.

The very next page displayed is the Settings page with a search bar at the top. Type “content settings” into the search bar.

As shown in the image below, click the “Content settings” selection that is highlighted.

When shown “Content settings,” click the “Cookies” selection (should be the first option shown).

When shown “Cookies,” find the option “See all cookies and site data” and click this option.

When shown “All cookies and site data,” now type in the secondary search box the name of the cookie you suspect is causing the 400 Bad Request Error.

In this tutorial, I’ve typed in “godaddy” as shown in the image. It’s worth noting that cookies can be deleted by a single or multiple.

Since I know it’s a GoDaddy cookie causing the 400 Bad Request Error, I’m opting to remove ONLY all GoDaddy cookies by clicking the “Remove All Shown” text just under the secondary search box containing the “godaddy” text.

Once “Remove All Shown” or the trash can icon for a singular cookie as been clicked, the following confirmation appears to verify your request.

If you’re certain that you would like to proceed with the request and deletion of selected cookies, then by all means, select the “Clear All” button.

This deletes the cookies, and you should now be able to kiss the 400 Bad Request Error bye-bye. Just that easy!

Watch the Video to Fix 400 Bad Request Errors.

And, of course, for those who do not want to read and follow step-by-step instructions, feel free to watch this quick 5-minute video! 😉