FIX: HTTP error 400 on Windows 10 computers
Also known as Bad Request error, the 400 error is a HTTP response status code that just means you made an incorrect request, or it was corrupted and the server was unable to understand it.
The error is usually caused when you enter the wrong URL in the address bar, what is known as invalid syntax. This can be frustrating and a challenge when it comes to fixing the problem, as the codes represent complex relationships between the client and web app, web server, and multiple third-party web services.
Usually, status codes in the 4xx category are client based error responses, and when you get one, it doesn’t necessarily mean it’s a client related issue i.e. your web browser or device you’re using to access the web.
However, because the 400 Bad Request error usually stems from the client side, the issue has to be resolved from therein.
Before trying the solutions below, make a thorough backup especially if you were making modifications to your site or app, so that you have a clean ground from which to test if the solutions below helped resolve the 400 Bad Request error.
FIX: 400 – That’s An Error – The Requested URL Was Not Found on This Server.
- Check your URL
- Clear cookies
- Upload smaller files
- Sign out and sign in again
- Check common software packages on the server
- Troubleshoot your server
- Reset your browser (Chrome)
1. Check your URL
The 400 Bad Request error usually happens when you type a wrong or incorrect URL, so the first step would be to check if the URL is correct. Check for spellings, cases, path, query or fragment portions after the domain name, and ensure they’re correct. Also check for improper special characters.
2. Clear cookies
An invalid or duplicate local cookie can cause 400 Bad Request Error to display when it is conflicting with another session token for a different user, so one of you gets the error. In this case, check for cookies relevant to the site or app that is bringing up the issue.
Here’s how to clear cache and cookies if you’re using Google Chrome, Microsoft Edge (IE) or Firefox browsers.
- Open Chrome and click More
- Click More tools
- Select Clear browsing data
- Choose a time range
- Select All time to delete everything
- Go to Cookies and other site data and Cached images and files, then check both boxes
- Click Clear data
- Open Microsoft Edge
- Click Hub>History
- Select Clear all history
- Choose what you want to remove then select Clear
- To clear cloud browsing history if you use Cortana, select Change what Microsoft Edge knows about me in the cloud, and click Clear browsing history.
You can delete cookies for one website or delete all cookies altogether. For one website, do this:
- Click Menu and select Options
- Click Privacy & Security
- Go to Cookies and Site Data
- Click Manage Data button
- In Search websites field, type the name of the site you want to remove cookies for
- Click Remove all shown to remove all cookies and storage data. Click Remove selected to remove selected items
- Click Save changes
- In Removing cookies and site data confirmation box, click Remove
To remove all cookies, do this:
- Click Menu and select Library
- Click History
- Click Clear Recent History
- Set Time range to clear to Everything
- Click the arrow next to Details to expand the list
- Select Cookies
- Click Clear Now and exit
3. Upload smaller files
The 400 Bad Request error could also be caused when you try to upload large files. Try and upload a smaller file and see if it helps. This includes uploads that aren’t from your computer or files sent to other computers that are deemed uploads from the server in your web app.
4. Sign out and sign in again
If the web app has user authentication, try signing out and sign in again. If you cleared cookies, you should be automatically logged out when you try loading the page again. The 400 Bad Request error could be coming up due to a string from the previous session sent from the server to client to identify it for future requests.
5. Check common software packages on the server
You could be running some software or content management systems that once modified could result in the 400 bad error request. To resolve this, do the following:
- Roll back recent upgrades of the software to a time before the error appeared and things worked fine
- Revert also to previous versions of extensions or modules you recently upgraded
- Uninstall new extensions, modules or plugins
- Check for database and manually look through records modified by extensions or plugins.
— RELATED: How to fix HTTPS error in Google Chrome
6. Troubleshoot your server
- Check for invalid HTTP headers
- Look through server-side logs of what the app did like requested pages, servers the app connected to and database results it provides.
- Debug application code or script. Do this manually and make a copy of the app to a local development machine before performing a debug process so you can recreate the exact scenario before the 400 Bad Request error happened
7. Reset your browser (Chrome)
- Open Chrome
- Click More
- Click Settings
- Click Advanced
- Under the Reset section, click Reset
- Confirm by clicking reset
Note: This process resets the default search engine back to Google, the homepage and tabs, new tab page, pinned tabs, content settings, cookies and site data, extensions and themes. The new settings will also apply across all devices you’re signed into.
Let us know if the solutions above helped resolve 400 – that’s an error – the requested URL was not found on this server, by leaving a comment below.
RELATED STORIES TO CHECK OUT:
- Windows 10 browser not working [FIX]
- Fix: Your Browser has Been Locked in Windows 10, 8, 8.1
- How to fix VPN issues on the Opera browser
Firefox has announced that it will start to warn users if they visit any breached sites. This is in an attempt to not only make […]
Oh dear. It’s been a pretty bad month for Microsoft concerning its Windows 10 October 1809 Update release. Microsoft eventually released the update a couple […]
Yesterday, Microsoft released Visual Studio 15.9. With it came the announcement that “developers now have the officially supported SDK and tools for creating 64-bit ARM […]