646196 - 400 Bad request

Status: RESOLVED WORKSFORME

(Firefox :: General, defect, P1)

Description

[Magno]

User-Agent:       Mozilla/5.0 (X11; Linux i686; rv:2.0) Gecko/20100101 Firefox/4.0
Build Identifier: Mozilla/5.0 (X11; Linux i686; rv:2.0) Gecko/20100101 Firefox/4.0

400 Bad request
Your browser sent an invalid request. 

Reproducible: Always

Comment 1

[Jo Hermans]

I'm not seeing that. Maybe a temporary error, or an error in one of the webservers (if there are multiple) ?

Comment 2

[Matthias Versen [:Matti]]

Please clear the disk cache and cookies under ctrl+shift+del.

Comment 3

[Thomas Ahlblom]

Unable to reproduce with a new profile in:
Mozilla/5.0 (X11; Linux i686 on x86_64; rv:2.2a1pre) Gecko/20110401 Firefox/4.2a1pre

Magno, are you still able to reproduce this problem?

Comment 4

[Magno]

Yes
Yes, when I try to go the address 4shared.com, I recieve ever the same response:
400 Bad request
Your browser sent an invalid request.

Comment 5

[Magno]

I have already cleaned the cache and rebooted, but still have the same problem.

Comment 6

[Jo Hermans]

Magno, are you using a proxy server ?

Does it also happen in Safe Mode, when all you add-ons are off ? The easiest way to test that is with this menu-entry [Help->Restart with Add-ons disabled]

Comment 7

[Thomas Ahlblom]

Magno, if you visit http://kluge.in-chemnitz.de/tools/browser.php what does "entire request sent by your browser" say?

Comment 8

[Leonard Camacho [:lcamacho]]

Tested and can't be reproduced 

Build: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:2.2a1pre) Gecko/20110401 Firefox/4.2a1pre

Build: Mozilla/5.0 (X11; Linux x86_64; rv:2.2a1pre) Gecko/20110401 Firefox/4.2a1pre

Comment 9

[u279076]

Magno, in addition to the already requested information, can you please provide the Firefox locale and your physical location? This may be an issue with proxy or accessing this site from within a particular domain.

Comment 10

[Magno]

Ok, problem solved, it was actually the cache after he cleaned the page loaded normally.
Thanks.

Comment 11

[Tim (fmdeveloper)]

Marking as WFM - Fixed is only used when a specific code change resolved the issue.

Comment 12

[Mike]

Hi, this issue is probably not fixed and probably relates to character encoding in cookie values with IIS based web servers which is why it can be difficult to reproduce.

The #1 scenario where this occurs is Google Analytics URLs where the campaign name in the query string include a character such as ’ (right single quote mark).

eg a campaign name containing Mother’s day (utm_campaign=Mother’s+day)

These are typically in links from email newsletters, ads, etc.

The standard Google Analytics javascript code saves these URL values into cookies.

Firefox encodes these differently to other browsers so that a ’ (right single quote mark) becomes 0x19.

After a refresh and once the cookie has been sent to an IIS based server, the server will always respond with 400 Bad Request until the cookie is deleted.


TEST CASE

You can test this scenario with: document.cookie="test=’";

In Firefox (Mac/Win) a cookie will be saved with the value: 0x19

In Chrome and IE a cookie will be saved with the value: ’ (Safari will ignore the cookie which is another quirk)

The Firefox cookie containing 0x19 will fail against IIS servers.


There are two issues:

- Firefox encoding of special characters into cookies
- IIS handling of special characters in cookies (which needs to be reported to Microsoft)

Regards,
Mike

Comment 13

[Matthias Versen [:Matti]]

Mike: Please open a new bug in the core:Networking cookie component.

Comment 14

[Mike]

Already opened under core:network as bug 654652