What is 400 Bad Request?
When I try to enter my user ID & password into certain sites, I get the message: Your browser sent a request that this server could not understand. - and 400 Bad Request appears on the tab. This seemed to have begun occurring around the time I disabled most of my plug-ins to troubleshoot another problem I was having. Enabling the plug-ins again did not help this new problem. I've just uninstalled ff, dumped my profile, reinstalled and still have the same problem! Any help out there?
Additional System Details
A few times a week
This started when...
I think when I disabled some plug-ins (see above)
- Gecko default plugin
- Runs Java applets using the latest installed versions of Java. For more information: Java Embedding Plugin. Run version test: Java Information.
- npmnqmp 071505000006
- Yahoo! Installer Plug-in provides application installation support
- Adobe Shockwave for Director Netscape plug-in, version 11.0.0
- Java Plug-In 2 for NPAPI Browsers
- The Flip4Mac WMV Plugin allows you to view Windows Media content using QuickTime.
- Shockwave Flash 10.1 r53
- The QuickTime Plugin allows you to view a wide variety of multimedia content in web pages. For more information, visit the QuickTime Web site.
- Simple plug-in that handles Citrix connection files
- User Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.5; en-US; rv:184.108.40.206) Gecko/20100914 Firefox/3.6.10
Enabling the plug-ins again did not help this new problem.
I've just uninstalled ff, dumped my profile, reinstalled and still have the same problem! Any help out there?
Clear the cache and the cookies from sites that cause problems.
- "Clear the Cache": Firefox > Preferences > Advanced > Network > Offline Storage (Cache): "Clear Now"
- "Remove the Cookies" from sites causing problems: Firefox > Preferences > Privacy > Cookies: "Show Cookies"
Thanks for the reply, but neither of the suggestions worked. I feel a little better knowing a couple other people are experiencing the same problem and would be interested if clearing the cache and removing cookies worked for anyone else. Here's another message I get along the same lines when placing an item in cart on quill.com:
Your browser sent a request that this server could not understand. Reference #7.b4daf180.1287607830.0
I've been getting this error multiple times a day on just ONE of my sites (a traffic exchange). It only happens in FireFox...I can view the site in IE, Chrome and Safari. Hosting company says it's not on their end. This is extremely frustrating as my TE is a business and FireFox is used by the majority of my members....when they can't surf they go to another TE.
If clearing the cookies doesn't help then it is possible that the file cookies.sqlite that stores the cookies is corrupted.
Rename (or delete) cookies.sqlite and cookies.txt, if they exist, in the Profile Folder in case cookies.sqlite got corrupted.
None of these suggestions above worked for me. I just started getting these 400 errors the last couple of weeks. Everything works fine on IE. When I reload the page after a 400 error it redirects fine to the page, but that's kind of annoying to do that every time. I've cleared all the cookies, cache, etc. I disabled all Add-ons. I cleared all my temporary files on my computer and uninstalled Firefox and re-installed it. I even looked for the cookies.sqlite and cookies.txt and they are not there. Any other suggestions anyone?
See Help > Troubleshooting Information > Profile Directory: Open Containing Folder
I have no back/forward button and I'm NOT going to pay someone to help me fix it. I prefer Mozilla Firefox and have encouraged dozens to use it but there is NO support and again, I'm not going to pay for support. Internet Express, which I hate, does have back/forward button so what the heck is going on with Firefox? You make PLENTY of money selling ads etc so get it together if you want us to continue using your browser. Or we will leave. :/
If the menu bar is hidden then press the F10 key or hold down the Alt key, that should make the menu bar appear.
Make sure that toolbars like the "Navigation Toolbar" and the "Bookmarks Toolbar" are visible: "View > Toolbars"
- If items are missing then open the Customize window via "View > Toolbars > Customize" or via "Firefox > Options > Toolbar Layout"
- If a missing item is in the toolbar palette then drag it back from the Customize window on the toolbar
- If you do not see an item on a toolbar and in the toolbar palette then click the "Restore Default Set" button to restore the default toolbar set up.
When will this bug be address. It appears from 3.5 to 7.0.1. If we test the links in safari, internet explorer, and opera all of the recent version and the links work.
So the question is when will this be address, if the browser recieves a 400 Bad Request then is should not cache the response, and attempt to resolve the link again when the user refreshes.
Not clear what is the problem.
Bad request messages started Monday with 8.0.1, Cleared everything uninstalled 4 times checked everything and still no cigar Chrome and IE working fine. I would prefer using Firefox...please issue fix
Tried all of the above. Firefox is preventing an upload of an extension for Joomla. The extension did upload ok when I used Explorer. Prefer Firefox to work. Found elsewhere a suggestion to disable all add-ons in Firefox - THIS WORKED!
Modified by mods315
I have been to dozens of different forums experiencing a bad request error. In all of these the answer is the same:
Clear the cache and the cookies from sites that cause problems. "Clear the Cache": Firefox > Preferences > Advanced > Network > Offline Storage (Cache): "Clear Now" "Remove the Cookies" from sites causing problems: Firefox > Preferences > Privacy > Cookies: "Show Cookies"
The question remains as to WHY this is occurring. There should not be a need to clear cookies every time. The company I work for emails customers video links (which surprise, surprise are not working in Firefox). It would be unreasonable to ask them to clear their cache and cookies prior to opening video link. Mozilla, the root of the problem is not being addressed. Why is it that all of a sudden so many pages are resulting in a bad request error?