266962 - file transfer reported as complete when in fact the connection was closed prematurely

Status: RESOLVED WORKSFORME

(Core Graveyard :: File Handling, defect)

Description

[Jason Proctor]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.3) Gecko/20040910
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.3) Gecko/20040910

my network connection has been kinda flaky the last few days, with connections
being dropped suddenly, etc. usual stuff. during a long file download, if the
connection is dropped before it is complete, mozilla will report that it is
complete and that the entire file was transferred. when, in fact, only a
fraction of the file was actually transferred.

Reproducible: Sometimes
Steps to Reproduce:
1. make your network flaky
2. download a big file
3. pull the connection somehow
4. note that when the connection drops, mozilla claims it all worked fine
5. note that the file is way smaller than it should be

Actual Results:  
the downloaded file was way smaller than the stated length, but mozilla claims
that it was completely downloaded. wget reports that the HTTP headers for that
download correctly state its size - and indeed, wget on the same flaky
connection has several goes at downloading the file and eventually succeeds
properly.

Expected Results:  
mozilla should have reported to me that the connection dropped, and given me the
choice of abandoning the download or trying to continue it (from where it left
off, like wget does).

no error messages at all. download window reports successful download.

Comment 1

[Darin Fisher]

-> Download Manager

(I suspect that the Download Manager is not handling networking errors properly.)

Comment 2

[Christian :Biesinger (don't email me, ping me on IRC)]

how did you download? save link target as, or via the helper app dialog?

Comment 3

[Jason Proctor]

(In reply to comment #2)
> how did you download? save link target as, or via the helper app dialog?

option-click on file link, which brings up the save as dialog. click OK there, download starts.

Comment 4

[Mathieu Malaterre]

Another simple way to reproduce is try to download the file jasper-1.200.zip
from the page:
http://web.archive.org/web/20010609195543/www.ece.ubc.ca/~mdadams/jasper/download.html

or the full link is:
http://web.archive.org/web/20010612151614/www.ece.ubc.ca/~mdadams/jasper/software/jasper-1.200.zip

Using konqueror you get a message box that the connection was closed, wget on
the command line also confirm that the connection was closed and thus download
was incomplete.

Can somebody please change:
OS from MacOSX to All since I can reproduce on GNU/Linux debian testing.
Using Firefox from debian testing (firefox 1.0.4)
Also change Mozilla application Suite to Firefox, since I believe it will draw
more attention to this bug.

Comment 5

[Gail Scully]

I don't understand this testing or the results I just know this thing is so screwed up that it has some server attached, the software is changed, it downloads separate disks instead of installing them and it is driving me crazy!!!!!!!!Help!!!!!!

Comment 6

[Serge Gautherie (:sgautherie)]

Jason, (Mathieu,)

Can you reproduce with SeaMonkey v1.1.9 ?
(or Firefox v2.0.0.14 ?)

Comment 7

[Robert Kaiser]

I suspect the new download manager backend in bug 381157 will solve this.

Comment 8

[Frankie]

Haven't seen this sort of error for many years. Presumed fixed as per comment 7.