Closed Bug 483613 Opened 16 years ago Closed 16 years ago

400 Bad Request

Categories

(Firefox :: General, defect)

3.0 Branch
x86
Windows Vista
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: tuckerdw, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.7) Gecko/2009021910 Firefox/3.0.7 (.NET CLR 3.5.30729) Creative ZENcast v2.01.01 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.7) Gecko/2009021910 Firefox/3.0.7 (.NET CLR 3.5.30729) Creative ZENcast v2.01.01 Receiving constant 400 bad request your browser sent an invalid request while navigating Facebook.com Reproducible: Always Steps to Reproduce: 1.logon Facebook 2.browse a friend's info page 3.receive message Expected Results: dispalys Facebook info with 400 Bad Request message
Hardware: x86 → Other
Which Addons are you using ?
Hardware: Other → x86
Version: unspecified → 3.0 Branch
I am not using any add-ons. Plugins: Adobe Acrobat, Java, Mozilla default plugin, Quicktime plugin 7.6, Shockway Flash, Shockwave for Director, Windows Presentation Foundation
Hardware: x86 → Other
You cleared the platform field and you are on windows, that means you are either using x86 or x86_64 :-) Any third-party tools that mess around with our files like spybot, ccleaner or a firewall that modifies http requests ? Did you tried clearing the facebook cookie ?
Hardware: Other → x86
Okay, I'm using X86. I was already bitten by spybot so I no longer use and I do not use ccleaner. I use McAfee Security Center for virus and firewall protection. I cleared my cookies and that fixed the problem. Thanks & take care!!!
You can clear single cookies in the options. I will mark this wfm unless you get this again and have a clue why this happens. I asked for the tools because some are modifying our cookie files and it can happen because they don't do it correctly.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.