Closed
Bug 211304
Opened 21 years ago
Closed 20 years ago
downloaded file is corrupted.
Categories
(SeaMonkey :: Download & File Handling, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 183291
People
(Reporter: nounours18200, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; fr; rv:1.3.1) Gecko/20030425
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; fr; rv:1.3.1) Gecko/20030425
This pb occurs on MANY other links : when a file is downlaoded, it is often
corrupted and unusable : it has to be redownloaded by using another download
manager such as "Download Accelerator Plus" for example.
Consequently I have systematically to use another download manager, because I
never know if the downloaded file will be correct or corrupted.
It also seems to me that the total download time is too short compared to the
size of the files: like if a part was not really downloaded.
Reproducible: Always
Steps to Reproduce:
1.do to the abovementionned link
2.download the file using the Mozilla download manager
3.try to unzip the file with winzip or equivalent, and you will get a message
saying the file is corrupted.
Actual Results:
I cannot unzp the file, so I have to redownload it by using another download
manager, such as "Download Accelerator Plus" for example.
Expected Results:
it should simply have downloaded the file without corrupting it.
Comment 1•21 years ago
|
||
Localizations shouldn't have anything to do with the functionality of the
download manager.
Reporter: can you attempt to reproduce with a recent nightly? I haven't had any
trouble using the download manager in quite a while.
Component: French/fr-FR → Download Manager
Product: Mozilla Localizations → Browser
Version: unspecified → Trunk
Updated•21 years ago
|
Assignee: bellot → download-manager
Updated•20 years ago
|
Product: Browser → Seamonkey
Comment 3•20 years ago
|
||
*** This bug has been marked as a duplicate of 183291 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•