282385 - Download manager downloads a file incorrectly

Status: RESOLVED EXPIRED

(Toolkit :: Downloads API, defect)

Description

[Patrick Bakker]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

I downloaded a Red Hat Enterprise Linux (RHEL) Enterprise Server (ES) 4 for x86
ISO file from my Red Hat Network (RHN) account. The web page indicates that the
file should be 168,669,184 bytes (confirmed by others). Downloading it with
FireFox resulted in a file 337,339,068 bytes. This is 700 bytes shy of exactly
2x the original file.

Reproducible: Didn't try

Steps to Reproduce:
1. I just downloaded the ISO from my RHN account. This is through an https:\\
connection with a long URL.

Actual Results:  
I redownloaded the file using the command-line program curl and it worked fine.

Comment 1

[Patrick Bakker]

Another person commented on Red Hat's nahant mailing list of 15 Feb 2005:
"I use firefox also and have noticed that when I right click on the link and
"Save Link As...", the file is occasionally bloated... but if I just click on
the link and let the download manager take over, it comes across ok

for whatever thats worth"

Comment 2

[OstGote!]

Was the file a gz/tgz or so? Probably the file is getting uncompressed on the
fly, so renaming it to .tar should be a workaround.

See Bug 233047 and bug 235859.

Comment 3

[Patrick Bakker]

It was an .iso file not an .iso.tgz or .iso.bz2 file. I don't think it can be
uncompressed.

Comment 4

[OstGote!]

Could you please check the HTTP headers from the server for this file? For
example with http://web-sniffer.net/.

Comment 5

[Jo]

I also have that problem, but I also have a fairly dodgy connection currently
(BT Yahoo! are upgrading their servers). In the meantime, use a proper FTP
downloader or something.

Comment 6

[Gervase Markham [:gerv]]

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 7

[Gervase Markham [:gerv]]

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.