Closed Bug 196038 Opened 23 years ago Closed 23 years ago

fails downloading files bigger than free space on disk cache

Categories

(Core :: Networking: Cache, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 69938

People

(Reporter: spamui, Assigned: gordon)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030210 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030210 When downloading big files (say 1 GB) from http and saving them to network drive, download manager saves them in diks cache only. When disk containig cache becomes full, download fails. There is enough free space on the destination drive. The free space on the disk containig cache is bigger than the maximum cache size setting. To avoid this bug, download process should save big files directly on the destination disk. Reproducible: Always Steps to Reproduce: 1. Place browser cache on drive with limited space. 2. Download file from http bigger than the free space on the disk containing cache saving it to other disk containig enough free space. 3. Wait for the download fail. Actual Results: Download failed Expected Results: Mozilla should have saved the file directly to the destination disk and downloaded file successfully cache size setting - 50000 KB free space on the drive C containig cache - 300 MB download size - 600 MB free space on the destination drive - 17 GB
i think IE has the same behavior [left-click] a link and the file starts downloading to the system drive. Meanwhile a save-as dialog appears and after download the file is moved to the chosen location. If you RIGHT-click a link and choose "Save target as" the d/l won't start just yet, but you first choose the location and the file is loaded directly to the specified location. Try that, if that works as inteneded this one is "invalid"
*** This bug has been marked as a duplicate of 69938 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.