At Fixya.com, our trusted experts are meticulously vetted and possess extensive experience in their respective fields. Backed by a community of knowledgeable professionals, our platform ensures that the solutions provided are thoroughly researched and validated.
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
Check for errors in the URL. The most common reason for a 400 Bad Request error is because the URL was typed wrong or the link that was clicked on points to a URL with a specific kind of mistake in it, like a syntax problem.
Important: This is most likely the problem if you get a 400 Bad Request error. Specficially, check for extra, typically non-allowed, characters in the URL like a percentage character. While there are perfectly valid uses for something like a % character, you won't often find one in a standard URL.
Clear your browser's cookies, especially if you're getting a Bad Request error with a Google service. Many sites report a 400 error when a cookie it's reading is corrupt or too old.
Clear your DNS cache, which should fix the 400 Bad Request error if it's being caused by outdated DNS records that your computer is storing. Do this in Windows by executingipconfig /flushdns from a Command Prompt window.
Important: This is not the same as clearing your browser's cache (next thing to try below).
Clear your browser's cache. A cached, but corrupt copy of the web page you're trying to access, but are getting the 400 error on, could be the root of the problem. Clearing your cache is unlikely the fix for the majority of 400 bad Request issues, but it's quick and easy, and so worth trying.
While this is not a common fix, try troubleshooting the problem as a 504 Gateway Timeoutissue instead, even though the problem is being reported as a 400 Bad Request.
In some relatively rare situations, two servers may take too long to communicate (agateway timeout issue) but will incorrectly, or at least unhelpfully, report the problem to you as a 400 Bad Request.
Contact the website directly that hosts the page. It's possible that the 400 Bad Request error actually isn't anything wrong on your end and it's something they need to fix, in which case letting them know about it would be very helpful.
Clear your browser cache (temporary internet files) & cookie And again try to load you tube. If that doesn't work, use a different browser. E.g. Firefox, Google Chrome, Opera. NOT IE. If that doesn't work, then use Proxy.
For an explanation about the "400 Bad Request" visit http://www.checkupdown.com/status/E400.html
Hi, If "your browser sent a request that this server could
not understand"
and "size of request header field exceeds server
limit", your request
is a bad or oversized cookie. (The same thing is true for
"Error 400").
For some very strange reason, it seems 9 of
10 Bad Request messages implicate Firefox.
Simply delete your "Cookies" and everything
will be okay. Don't worry about erasing them;
nothing bad will happen. You won't lose your
internet browser's "Bookmarks" or
"Favorites".
The worst thing that could happen is you will
be asked to retype your username/password
when you return to YouTube and some other
websites -- that's all.
As you're dumping your cookies, you should
also erase all your "Temporary Internet Files"
and "History". This will render your computer
totally "fresh" in YouTube's eyes. It would be
best if you shutdown / reboot after doing this:
Internet Explorer 6:
> Tools > Internet Options
> Delete Cookies > OK
> Delete Files > OK
> Clear History > Yes
> OK
Internet Explorer 7:
> Tools > Internet Options > Delete...
> Delete files > Yes
> Delete cookies > OK
> Delete history > OK
> Close (browsing history window)
> OK
If this is the same Bad Request problem that's going around for
everyone else, the problem is solved by clearing cookies. BUT,
clearing cookies is a TEMP fix
clear the cache and delete the cookies from site(s) that cause problems:
Tools > Options > Advanced > Network > Offline Storage (Cache): "Clear Now" Tools > Options > Privacy > Cookies: "Show Cookies"
If
that didn't help then try to rename or delete cookies.sqlite and
cookies.txt (if it exists) in the profile folder in case there is a
problem with the file.
Try clearing your cache and restarting your browser. On Firefox, you can do this by going to the Tools > Clear Private Data option. In Internet Explorer, go to
Tools > Internet Options > Internet Properties > General > Delete Browsing History > Delete All Temporary Files.
cant restore google as my homepage
×