Closed
Bug 671852
Opened 14 years ago
Closed 14 years ago
Default character encoding are different between mirror servers
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: alice0775, Assigned: nmaul)
Details
Attachments
(1 file)
104.23 KB,
image/png
|
Details |
Build Identifier:
http://hg.mozilla.org/mozilla-central/rev/52617959b48e
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0a1) Gecko/20110715 Firefox/8.0a1 ID:20110715030758
Default character encoding are different between mirror servers.
The look of the page changes. see attachment.
Reproducible: Always
Steps to Reproduce:
1. Start firefox with New Profile (without addons)
2. Open In New Tab http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/tracemonkey-win32/
3. Open In New Tab http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-central-win32/
4, Reload them several times to change mirror server
Actual Results:
Mirror sever : character encoding
dm-ftp01.mozilla.org : ISO-8859-1
ftp1.dmz.sjc1.mozilla.com : UTF-8
ftp2.dmz.sjc1.mozilla.com : UTF-8
* maybe not all
Expected Results:
character encoding should be constant between mirrors.
Comment 1•14 years ago
|
||
huh, I didn't think dm-ftp01 was even in the pool anymore.
Assignee: justdave → server-ops
Component: FTP: Mirrors → Server Operations
Assignee | ||
Comment 2•14 years ago
|
||
This was caused by a different default between our RHEL5 and RHEL6 configs. Should be fixed now, along with a few other minor differences.
To be clear, I updated dm-ftp01 to use UTF-8... seemed like the more i18n-friendly thing to do.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•14 years ago
|
Assignee: server-ops → nmaul
![]() |
Reporter | |
Updated•14 years ago
|
Status: RESOLVED → VERIFIED
![]() |
Reporter | |
Comment 3•14 years ago
|
||
ftp.mozilla.org Port 80 returns ISO-8859-1,
Is this intentional?
Assignee | ||
Comment 4•14 years ago
|
||
For better or worse, yes, that is intentional.
The particular reason is that Apache's auto-index pages like that are served with the charset of the underlying filesystem... in this case, it's an NFS mount, and apparently it was not set up as a UTF-8 volume.
I can force Apache to return UTF-8, but this won't have any good effect. The README header shown at the top of the page is not localized- there is only that one (English) version. Additionally, the actual filenames and directory names would still all be English.
If you can find a page that looks wrong, we can try forcing it and see what happens. :)
![]() |
Reporter | |
Comment 5•14 years ago
|
||
OK Thanks. and I am sorry bug spam.
Updated•10 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•