4 ms·

This is interesting. What conditions would make a file too big for a browser download? If the server supports range requests (I'm almost certain Nextcloud does)

• parliament32 6y ago
  It's technically possible, but most browsers don't auto-resume, and most webservers will timeout a request after a certain amount of time has elapsed. You can get around all this with browser extensions, but it's honestly easier to use a more robust protocol (this is in the context of, say, a 10TB file that'll take you a few days to download).
  • anderspitman 6y ago
    I don't see how anything would be much more robust than HTTP. Any network based protocol can fail at any time, so you're going to have to have some concept of tracking your progress and retrying failed requests. Both are easy to do with HTTP. Can you give a concrete example of something that would work better than HTTP?
    • parliament32 6y ago
      Here's an exercise for you: In your browser, start downloading a test file, like [1]. Turn off your network card for a few seconds, then turn it back on. See what your browser does. Next, start downloading a large file over Bittorrent, like [2]. Turn off your network card for a few seconds, then turn it back on. See what the client does. [1] http://speedtest.tele2.net/100GB.zip http://speedtest.tele2.net/100GB.zip [2] https://cdimage.debian.org/debian-cd/current/amd64/bt-dvd/debian-10.5.0-amd64-DVD-1.iso.torrent https://cdimage.debian.org/debian-cd/current/amd64/bt-dvd/de...
      • anderspitman 6y ago
        This has nothing to do with HTTP. It's just poor behavior on the part of the browser.