Allow resuming transfers. Support byte ranges.

[barkoder]

Official Instance

• [X] The bug is reproducible on the official hosted instance, or is API-related.

Describe the bug

Hi.

Don't know if I should file this under "bug report" or "feature request". So here it goes.

I used the API of the official instance to curl a video to my computer - http://pipedihonqyp5fh3ffn5c7i2zlg4lljc4gorefhpydtqiapewy5gprad.onion/streams/vWF3IDk9Gek

The transfer was interrupted 75% of the way through and I got this error

curl: (18) transfer closed with 427825322 bytes remaining to read .

To resume the transfer I used the curl continue flag -C - and I got

curl: (33) HTTP server doesn't seem to support byte ranges. Cannot resume.

So I tried switching to several different instances. And it turns out that literally none of the available instances support byte ranges. So I can't resume an interruped transfer from any of them.

Is there a reason why this is the default? Is it possible to have all the API servers support byte ranges and allow resumption?

Thanks.

To Reproduce

0. Fire up tor, not Tor Browser with the default settings.

1. curl -s -x socks5h://127.0.0.1:9050 'http://pipedihonqyp5fh3ffn5c7i2zlg4lljc4gorefhpydtqiapewy5gprad.onion/streams/vWF3IDk9Gek' | jq

2. Pick a large file format.

3. curl -x socks5h://127.0.0.1:9050 -C - -R "hxxps :// FILE FORMAT THAT WAS PICKED AT STEP 2" -o file.webm to your computer.

4. Transfer may get interrupted.

5. If it does try the same command again, and make sure to not remove the -C - flag.

6. HTTP server doesn't seem to support byte ranges. Cannot resume.

Expected behavior

Transfer should resume wherever it was left off.

Logs/Errors

No response

Browser, and OS with Version.

curl 8.6.0

Additional context

No response