← Back to context

Comment by ruszki

16 hours ago

This trick means that there is a check when you resume a download compared to when you start one. Introduce that check to when a download is started.

The situation AFAICT is something like this: the server mints unique download URLs which can only be used once. This is generally so they can't be shared. It serves the URL to the first comer and when that connection drops (maybe with some timeout) subsequent requests to that URL produce 410 Gone. So if your download fails halfway through, you can't re-request the same URL with a Range, which is how normal resumption works. You need to get a new one-time URL minted and download that.

So from the browser's perspective, these are two distinct, unrelated URLs. There isn't a mechanism where it can know they are backed by the same file.

This browser behavior seems pretty reasonable. I'd try fixing it by doing something different on the server.