@GNUxeava http is a bit :neocat_googly: at file transfers. you can put in a content-length (or not? file could be "i'mma shit over the pipe until i close the link" length), and there isn't really a "did you recieve that correctly?" checksum, there isn't really a way to say "i still have 56% of that file before we shit the bed, can i have the rest?"

the closest is a range request, which is SUPPOSED to be supported by standards compliant servers but is it? :blobcatdunno:

rsync on the other hand rolling hashes files in to chunks, and communicates to itself (the other server also has rsync...) about what blocks are present and if they transferred OK, stuff like that. it's a pain. most people just shit the file over the pipe and assume nothing will ever go wrong. for sufficiently small data... it doesn't? or it does and you just retry.

when you have 2 gigabyte artifacts like torch .. :neofox_up_paws: