Closed
Bug 255539
Opened 21 years ago
Closed 20 years ago
Reload does not fetch againg http (server provided) header parameters
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: frasson, Assigned: bugzilla)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3
I realized that my web page, which used to validate in the w3c page, does not
validate anymore and it stopped to display non ascii characters correctly. I
investigated the problem and I discovered that in order to determine the
charset, a browser should look first in the HTTP header (whatever it means),
then in the <meta> fields in the header of the html file. Please see
http://www.w3.org/TR/html401/charset.html#h-5.2.2
to find
To sum up, conforming user agents must observe the following priorities when
determining a document's character encoding (from highest priority to lowest):
1. An HTTP "charset" parameter in a "Content-Type" field.
2. A META declaration with "http-equiv" set to "Content-Type" and a value
set for "charset".
3. The charset attribute set on an element that designates an external
resource.
I discovered that I could change the default charset that my server sends by
adding a file .htaccess containing
AddDefaultCharset iso-8859-1
When I did it, my page was not reloading correctly (same charset problem), but
it started validate correctly again. Them I cleaned the cache, and it started to
display correctly. So, "reload" does not reload everything :-(
I removed the file and repeated the process with my Mozilla version
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031114
and it reloads *correctly*. Strange, isn't it?
This behaviour is allways reproduced in firefox .9.3
Reproducible: Always
Steps to Reproduce:
1. Make sure that your HTTP server sends some charset on page request, and that
you can *change* that (or on server seettings or via .htaccess file)
2. Put a page in a different encoding so that it does not display well and open
firefox in this page. (To know what should change, please see the w3c page given
above.)
3. Change server settings
4. Reload and see if the page is now correctly displayed (not in my case)
5. Close Firefox and visit again the page (here still not correct)
6. Clean cache and visit page again (now ok for me)
Actual Results:
Reload does not get the new server settings (charset in my case).
Expected Results:
All page related content should be reload, not only the contents of accessed files.
Comment 1•20 years ago
|
||
This is an automated message, with ID "auto-resolve01".
This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.
While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.
If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.
The latest beta releases can be obtained from:
Firefox: http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 2•20 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•