Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • How big are we talking? I download ISOs all the time...
  • Much better solution:

    Install JDownloader 2. Just copy a link, and JDownloader will pick it up if it's running (otherwise, open it manually).

    It not only downloads the file and lets you resume the download, but can also download multiple pieces in parallel.

  • IDM and NDM are still the golden standards for download managers. I still can’t trust browsers. These things let me go to the source page where the download was captured from if it failed. Gets streaming video from most non drm sites. IDM is still getting updates.
  • Resumable downloads in firefox generally appear to be fairly unstable though. This has been a known problem in some form since as far back as 2005.

    It's odd how the experience differs so much; I clearly remember successfully resuming a download less than a month ago, and I don't remember any time Firefox had any problems with them. My network.http.response.timeout is the default of 300.

    There are reasons, but until someone actually publishes an article that's more detailed than the vagueness here, there's nothing anyone can really do about it.

  • I like using the aria2[0] download utility - I don't think I've downloaded anything bigger than a dozen megabytes through a web browser for the last several years, and this method allows me more protocols, multiple connections, and of course continuing downloads. That said, it's nice someone found a solution to the problem - makes life easier for everyone who doesn't use an external download utility... How do you even go about finding the solutions to bugs like this?

    [0]: https://aria2.github.io/

  • Based on the setting `network.http.response.timeout`, which is timeout related, I'm *guessing* Firefox cannot distinguish between a network EOF or a logical/request-level EOF?

    But that aside, it's kinda typical for a software from the developed world to have fault tolerance this bad. The engineer who wrote the code probably never ever annoyed by network error aside from a few well-known cases, and thus don't take these problems to their hearts.

    For example, have you tried to download big files with a connection that has 100ms ~ 20seconds latency jitter? That happens with crossborder connections in/out of China. And in India, your users sometime experiences power issue which set their router to reboot or redial, that also causes an interruption in download.

    Of course, people in these countries can't pay you much. But, these problems can all be solved/mitigated in software. Do you want to improve your software so it can be more robust, or do you want to waste user's time sitting in front your software just to get things done?

  • Who remembers Getright?

    https://www.getright.com/

  • I'll try this.

    The way I have to resume downloads in Firefox is

    1. Move the .part file to a temp file

    2. Start the download again; a new .part file gets created

    3. Pause the download

    4. Move the temp file to the .part file, overwriting it

    5. Unpause the download; it resumes from where the old .part file stopped

    This is only necessary if a "one-time" download link gets interrupted part-way through, eg. by a flaky connection. Attempting to resume a one-time link like normal gets (I assume) a 400 response and FF kills the .part file.

Explore Birbla archives