412262 - can't download files larger 4GB via HTTP

Status: RESOLVED WORKSFORME

(Core :: Networking: HTTP, defect)

Description

[Manuel]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11

I tried to download a ISO-image via HTTP, each time the download aborts at 105MB. When I use FTP instead everything works fine.

Reproducible: Always

Steps to Reproduce:
1. try to download a file that is larger 4 GB 
2. the portion of those files that is larger 4 GB will be downloaded
3. Download Manager shows download finished
4. File is visible in the local download location
Actual Results:  
only a portion of a file is being downloaded

Expected Results:  
the whole file should be downloaded

When the file is downloaded via FTP this problem does not occur

Comment 2

[Manuel]

I don't think that this is a duplicate of bug 184452

I tried to download another ISO image (http://ftp.tu-chemnitz.de/pub/linux/opensuse/distribution/10.2/iso/dvd/openSUSE-10.2-GM-DVD-i386.iso) which is approx. 3.7 GB big and this works via HTTP. In contradiction to the above mentioned bug there seems to me a "border" of 4GB and not a "border" of 2 GB.

Furthermore I investigated a little bit more and with FF 2.0.0.10 running on openSuse 10.3 both downloads (3.7 GB and 4.2 GB) worked perfectly.
In addition I tried the current IE7 as well as IE6 on W2K on different installations and the results are the same as with FF 2.0.0.11 the download aborts as described in my initial posting.

Comment 3

[Matthias Versen [:Matti]]

Do you use fat32 as file system ?

Comment 4

[Stephen Donner [:stephend] Not actively reading bugmail]

Try this build: ftp://ftp.mozilla.org/pub/firefox/nightly/latest-trunk/firefox-3.0b3pre.en-US.win32.installer.exe

Comment 5

[Manuel]

(In reply to comment #3)
> Do you use fat32 as file system ?
> 
No, I always use NTFS partitions on Windows systems

Comment 6

[Manuel]

(In reply to comment #4)
> Try this build:
> ftp://ftp.mozilla.org/pub/firefox/nightly/latest-trunk/firefox-3.0b3pre.en-US.win32.installer.exe
> 

In a first quick test it seems to be fixed in the nightly build version.

Comment 7

[Manuel]

(In reply to comment #6)
...
> 
> In a first quick test it seems to be fixed in the nightly build version.
> 
I can finally confirm that the problem is fixed in the mentioned FF3 build. Furthermore I talked to some colleagues and they bring to mind that it worked in FF 2.0.0.9 or 2.0.0.10 already.

Comment 8

[Stephen Donner [:stephend] Not actively reading bugmail]

wfm, based on comments

Comment 9

[Manuel]

So it works in FF3 but it did not work in FF 2.0.0.11

Comment 10

[Matthias Versen [:Matti]]

yes, but 2.0.0.11 is a one year+ old branch which only gets security fixes and fixes for topcrashes. You will never see a fix for this issue in the branch.

This is working in the developing trunk, that means there is nothing more to fix.
marking wfm again