User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3a) Gecko/20021212 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3a) Gecko/20021212 After download "finished" (by correct or incorrect way), Mozilla should check every downloaded file by MD5 and compare file size against expected size. Then: 1, If the size of downloaded file is incorrect, Mozilla should notice the user and offer to A, re-download (append) missing part of file B, re-download the whole file C, nothing 2, Everytime, Download manager should count and show MD5sum of file (e.q. in new column of Download Manager). User may then compare the sum against the expected sum. 3, Download Manager should have "re-download" option avaiable for any file. If I see, that MD5sum is not correct, or discover by other way, that file is broken, I simply choose some "Re-download" option in Download Manager and the download will start again, without any browsing, searching the site (Ooohh, where it was?), searching the link where the desired download started etc. Download Manager should keep the exact location in its log and while the file is in log, DM should be able to directly start the download again. Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: If download of file is broken, Download Manager states that it is "finished", regardless on HOW it is finished (correctly or not) Expected Results: Mozilla should be much smarter, as I explained before. Since now, there are special programs that "do the download". They are almost all commercial or shareware. Doing the correct download, I think, is essentially the job of browser and OS however -the OS tryes to do "dirty work" and browser should worry, if the download was done succesfully for the user. Since now, as far as I know, there is not browser that is such smart as I request from Mozilla. But what should be the most innovative and most powerfull browser, if not Mozilla? Internet Explorer? Surely not. Opera? Konqueror? I rate the Mozilla as the best and so my expections are high.

*** This bug has been marked as a duplicate of 164878 ***