Share this article
Improve this guide
Browser Sent a Request this Server Could Not Understand
This is a common error, but we have 3 ways of fixing it quickly
5 min. read
Updated onJune 17, 2024
updated onJune 17, 2024
Share this article
Improve this guide
Read our disclosure page to find out how can you help Windows Report sustain the editorial teamRead more
Key notes
Did you just see the error message,your browser sent a request that this server could not understand.Size of a request header field exceeds theserver limit?
Nothing to worry about since this is a common issue, and it often shows up when the server recognizes this as a generic client error.
Also, if you bump into theHTTP 400 error on Windows 10/11, you can refer to our detailed post for more information.
Fortunately, we have a few workarounds for you that will help you to get rid of the Bad Request 400 error on your browsers.
Why does my browser keep saying bad requests?
There are quite a few reasons why you may encounter the 400 Bad Request error that is not specific to any particular browser or OS (operating system), such as:
Before you proceed, make sure you check the submitted URL for any syntax error or if there’s an extra character like a % symbol, etc.
For a wrong URL, you can use a free online tool like theURL Decoder/Encoderto correct the domain name.
Below, we have listed some of the potential solutions that can help you fix the issue if the size of a request header field exceeds the server limit on Chrome/Edge/Safari/Firefox.
Even though some of the fixes work perfectly, you might encounter a situation where your only option is to switch to another browser like Opera One.
With Opera One, you ensure your data privacy with a free VPN and also surf the web worry-free with an Ad blocker and VPN. Besides, with integrated messaging apps and AI you will never be out of the loop.
Opera One
How do you fix a bad request your browser sent a request that this server could not understand?
1. Remove browser cookies
Now, restart Chrome and visit the problem website. You should not encounterthe error,400 bad request your browser sent a request that this server could not understandagain.
You can also remove cookies for Firefox, Edge, or Safari in a similar manner.
2. Disable the browser extensions
Now, relaunch the browser and check if the Bad Request error is resolved.
3. Flush the DNS cache
Once you see the success message, exit Command Prompt and check the website if the error still appears. This method is also applicable to all other browsers.
Once done, try visiting the problem website, and the error message,your browser sent a request that this server could not understand. Size of a request header field that exceeds server limitshould not show again.
What does the size of a request header field exceeding the server limit mean?
Usually, a very large Cookie triggers this error, and so the request header field exceeds the decided limit for the Web Server.
In this case, since you are on the client side (website/browser), simply clearing the cache of your web browser should fix the issue.
At the same time, check that the file size does not exceed the server file size limit, and trigger the size of a request header field exceeds server limiterror on Chrome/Edge/Safari/Firefox.
But if you encounter an error likethis website is not accessible, then you can follow our detailed guide for solutions.
A padding to disable MSIE and Chrome friendly error pagealso occurs if you have problems with your request, but we have a guide that can fix it, so don’t hesitate to check it out.
For any other queries on browsers or website errors, you can leave a message in the comments box below.
More about the topics:Browser errors,website
Madhuparna Roy
A diploma holder in computers and with a keen interest in technology, Madhuparna is passionate about writing How-to guides and helping people solve the most intricate Windows issues.
It all started with the evolution of mobile phones and Google, and that has now settled with Windows.
User forum
0 messages
Sort by:LatestOldestMost Votes
Comment*
Name*
Email*
Commenting as.Not you?
Save information for future comments
Comment
Δ
Madhuparna Roy
