- 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.
CauseThe 400 Bad Request error is an HTTP status code that means that the request you sent to the website server (i.e. a request to load a web page) was somehow malformed therefore the server was unable to understand or process the request.
Resolution
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 some kind of mistake in it.
Though it's rare, the 400 Bad Request error could be an issue with the web site's server that you are trying to access. You may want to attempt to contact the webmaster or another site contact and inform them of the error message. The webmaster of most Internet sites can be reached via email at webmaster@website.com, replacing website.com with the actual website name.
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
I too was getting the "400 Bad Request" message in Chrome but other browsers could go to the same web page without problem. I found the it was the DNS pre-fetching causing my error. I went into Options, then "Under the Hood" and unchecked "Use DNS pre-fetching to improve page load performance". Immediately my 400 error went away and hasn't been seen since.
Cause
The 400 Bad Request error is an HTTP status code that means that the request you sent to the website server (i.e. a request to load a web page) was somehow malformed therefore the server was unable to understand or process the request.
Resolution
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 some kind of mistake in it.
Though it's rare, the 400 Bad Request error could be an issue with the web site's server that you are trying to access. You may want to attempt to contact the webmaster or another site contact and inform them of the error message. The webmaster of most Internet sites can be reached via email at [email protected], replacing website.com with the actual website name.
Unable to fix Gmail Bad Request error 400 in Google chrome, visit our website to find easy to implement steps through which you can fix Gmail Bad Request error 400 very easily.
×