Closed Bug 241869 Opened 20 years ago Closed 19 years ago

MD5 checksums of downloaded .iso files do not match after downloading

Categories

(Core Graveyard :: File Handling, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: joost, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7b) Gecko/20040421
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7b) Gecko/20040421

When downloading ISO-images from FTP servers with Mozilla 1.7 RC1 on Windows
2000 (and XP too) the images get corrupted (the MD5 checksum doesn't match).
This happens with various images from various servers. Please note that i use
the "progress dialog", not the download manager.

Reproducible: Always
Steps to Reproduce:
1. Browse to the iso-image on the FTP server
2. Select "save as" and choose a location.
3. Wait till the download is finished and check the MD5 checksum

Actual Results:  
Checksum doesn't match MD5SUMS

Expected Results:  
MD5 checksum should match
WFM Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7b) Gecko/20040421

Is the file size of the downloaded file correct?
You said it happens on XP and 2000...  did you test on different machines, or
dual boot?
>Is the file size of the downloaded file correct?
The file size seems to be correct
>You said it happens on XP and 2000...  did you test on different machines, or
>dual boot?
It is tested on two different machines, however both machines have the same
hardware configuration (AMD Athlon 64 3200+, 1GB Mem) and are on the same
network (connecting to the internet through a Cisco Pix 501).
-> File Handling
Assignee: general → file-handling
Component: Browser-General → File Handling
QA Contact: general → ian
*** Bug 290348 has been marked as a duplicate of this bug. ***
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/
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: 19 years ago
Resolution: --- → EXPIRED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.