Skip to content

Fix: Your client has issued a malformed or illegal request

Frustrated with the 400 Bad Request - Your client has issued a malformed or illegal request on Google services? Learn how to fix it on any browser.

400 Bad Request occurs when we try accessing a webpage that isn’t available or requesting a secured page without proper credentials.

In order to fix the issue, verify the URL address, check in the private browser, and use proper credentials after clearing cookies and cache.

Your client has issued a malformed or illegal request

In this guide, we have shared the different methods for troubleshooting a computer’s malformed or illegal request message.

Method 1: Recheck URL Format

One of the primary reasons for this issue is the entering an incorrect URL.

In this regard, you should double-check the website address if you have mistakenly used backslashes instead of forward slashes or have incorporated an unsupported symbol, such as curly brackets.

Furthermore, although the site’s name isn’t case-sensitive, its directory might be. Just verify that everything is entered after the .com domain is precisely as it should be.

Method 2: Try Private Browsing Mode

It is no secret that third-party add-ons could lead to various 4XX errors. Therefore, the safest bet is to browse the web in private mode. Doing so will disable all the extensions, and you can verify if the extensions are the reason for the 400 error.

  1. Launch the Google Chrome browser.
  2. Keypress the Ctrl + Shift + N shortcut keys to open an Incognito Window.
    Use Google Chrome Incognito
  3. Now try accessing the site, causing the bad request error.

If it loads without any issue, the problem could be attributed to the installed extensions or cookie and cache clutter within the browser.

Method 3: Disable Browser Extension

Most issues while accessing the browser are generally caused by extensions that we have installed. They can conflict with the browser’s functionality.

  1. Launch the Chrome app on the computer.
  2. Visit the Chrome’s extensions pages at chrome://extensions/ address.
  3. Toggle the button to turn off the extension.
    Disable browser extensions on chrome computer
  4. Now disable each extension, one at a time, until the error has been fixed.

Moreover, it is recommended that the extensions that cause issues be uninstalled.

Method 4: Flush System DNS Cache

DNS is a record book containing all the Domain Names corresponding to their IP Addresses. But if this data gets outdated or corrupted, the browser won’t be able to establish a successful connection to the web. Therefore, it is recommended to clear the DNS cache:

  1. Open the Start Menu and search CMD.
  2. Launch the Command Prompt as an administrator.
    Run Command Prompt as Administrator
  3. Now type in ipconfig /flushdns, and hit Enter.
    Flush DNS and IPConfig in Windows command prompt

This will delete the DNS cache; hopefully, the error will rectify the issue. You should also consider clearing the DNS cache within the Chrome browser to be on the same page with the system.

Method 5: Delete Temporary Browsing Data

Over time, a lot of temporary data in the browser gets accumulated. This slows down the browser performance and could conflict with the proper loading of websites.

Deleting these cache and cookies files can help fix the underlying problem.

  1. Open the Chrome browser.
  2. Type in delete cache Chrome actions in the address bar.
  3. Click on Clear Browsing Data from the result list.
    Clear browsing data Google Chrome Actions
  4. Select Cookies and other site data and Cached images and files.
    Clear Cookies and Cache from Chrome Browser
  5. Hit the Clear data button and wait for the process to complete.

Deleting the cache will delay the site loading for a few extra seconds because the fresh files are fetched from the web server instead of browser storage.

Method 6: Verify Upload File Size

If you get this error while trying to upload a file, it could be due to the site’s maximum file size restriction.

So consider compressing the file to a RAR or ZIP format before uploading it to the web. You can also upload the file to the cloud and share the link with the concerned party.

Bottom Line

In my case, the DNS cache wasn’t in sync with the online records. As a result, the browser was still picking up old data and couldn’t establish a successful connection. Deleting this Domain Name Server (DNS) cache helped clear the 400 error code message.

We should also ensure that we aren’t accessing the gated page hidden behind the account sign-in.

Please share the article if you find it helpful:

Disclosure: This page may contain affiliate links, which means we may receive compensation for your purchases; of course at no extra cost to you (indeed, you may get special discounts).
Kushal Azza

Kushal Azza

Kushal Azza is a Google Certified IT Professional, Digital Content Creator, and Go-To Digital Marketer with Engineering Degree. He has over a decade of experience solving tech problems, troubleshooting, and innovating digital solutions. Follow him on Twitter and LinkedIn.

Leave a thought or feedback

Please leave a descriptive comment or feedback with your real name. Our human moderator vets every comment, and it may take 24 to 48 hours to get published or rejected.

Your email address will not be published, and we will never spam your inbox. Required fields are marked *