incorrect encoding cause two GET action on the server

RESOLVED INCOMPLETE

Status

()

Product:
Firefox
Component:
General
--
critical
RESOLVED INCOMPLETE
Reported:
9 years ago
Modified:
7 years ago

People

(Reporter: Dominique COLOMBANI, Unassigned)

Tracking

Version:
3.5 Branch
x86
Windows Vista
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [CLOSEME 2011-1-1])

(Reporter)

Description

•
9 years ago 
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; fr; rv:1.9.1.1) Gecko/20090715 Firefox/3.5.1 (.NET CLR 3.5.30729) FirePHP/0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; fr; rv:1.9.1.1) Gecko/20090715 Firefox/3.5.1 (.NET CLR 3.5.30729) FirePHP/0.3

When the actual encoding of a page don't agree with the encoding indicated in the header, Firefox send two GET requests to the server.

This is very ennoying if this happend on PHP page, which create new recors in a database. 


Reproducible: Always

Comment 1

•
9 years ago 
How about a sample URL that demonstrates this?

Comment 2

•
9 years ago 
Sounds like bug 61363?  But this shouldn't happen for a page that specifies a charset in an HTTP header (as opposed to in the HTML <head>).
(Reporter)

Comment 3

•
9 years ago 
Here is an exemple of PHP code :

<html>
<head>
<title></title>
</head>

<body>
<?php 
print "begin <br>";
print "éàù<br>";
print "end";
?>
</body>
</html>

Each time this page is load, I have two GET load in the log of Apache.

But I didn't notice that browser cache was disable (browser.cache.disk.enable : false).  If the browser cache is enable, I have only one GET.

Comment 4

•
9 years ago 
The headers could depend on your PHP installation, but this sure sounds like a dup of bug 61363.
Group: core-security

Comment 5

•
8 years ago 
Reporter, are you still seeing this issue with Firefox 3.6.12 or later in safe mode? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles
Whiteboard: [CLOSEME 2011-1-1]
Version: unspecified → 3.5 Branch

Comment 6

•
7 years ago 
No reply, INCOMPLETE. Please retest with Firefox 3.6.13 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.