搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

400 bad request error after Firefox 4.0.1 update

  • 4 回覆
  • 10 有這個問題
  • 8 次檢視
  • 最近回覆由 dcjoann123

more options

After the latest Firefox update, the browser no longer works. When I try to go to a web site, Firefox sends the URL incorrectly by repeating the url. For example: if I type the url http://my.yahoo.com/, I get the following error:

400 Bad Request

Your browser sent a request that this server could not understand:

my.yahoo.comhttp://my.yahoo.com/ (port 80)

After the latest Firefox update, the browser no longer works. When I try to go to a web site, Firefox sends the URL incorrectly by repeating the url. For example: if I type the url http://my.yahoo.com/, I get the following error: 400 Bad Request Your browser sent a request that this server could not understand: my.yahoo.comhttp://my.yahoo.com/ (port 80)

所有回覆 (4)

more options

Clear the cache and the cookies from sites that cause problems.

"Clear the Cache":

  • Tools > Options > Advanced > Network > Offline Storage (Cache): "Clear Now"

"Remove the Cookies" from sites causing problems:

  • Tools > Options > Privacy > Cookies: "Show Cookies"
more options

Thank you for your reply, but this did not solve the problem.

more options

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 (cookies.sqlite.old) and delete cookies.sqlite-journal and cookies.txt, if they exist, in the Profile Folder in case the file cookies.sqlite got corrupted.

more options

Thank you again for your help. After clearing the cache and cookies, and still having the problem, I uninstalled/reinstalled firefox. I had tried this before, but allowed it to keep my bookmarks, etc.. This time I had it remove everything (this is a check-box when doing the uninstall).

After reinstalling Firefox this time, the problem went away. Thank you for your help. Your comment about the cache and cookies, made me think that removing all information during the uninstall would help, and it did.

I don't know if your second suggestion would have helped, because it is now fixed. But I believe it was a possibility.