I've come to learn that LFTP can transfer files via HTTP. Why this is interesting to me is that ISP's can throttle and do throttle FTP transfer speeds. But they theoretically can't throttle HTTP streams. I've downloaded files directly from the rTorrent webUI and those downloads, while not being threaded, download crazy fast. While LFTP, using 10 threads and 1 file, cap out at about 40MB/s (for me). I've never seen it go any faster.
I can see the download path when DL'ing via HTTP so configuring the DL' path is not a problem. Authentication is going to be the same as SFTP transfers. All that needs doing is creating the correct syntax (but what do I know I'm not a programmer by any means).
I've come to learn that LFTP can transfer files via HTTP. Why this is interesting to me is that ISP's can throttle and do throttle FTP transfer speeds. But they theoretically can't throttle HTTP streams. I've downloaded files directly from the rTorrent webUI and those downloads, while not being threaded, download crazy fast. While LFTP, using 10 threads and 1 file, cap out at about 40MB/s (for me). I've never seen it go any faster.
I can see the download path when DL'ing via HTTP so configuring the DL' path is not a problem. Authentication is going to be the same as SFTP transfers. All that needs doing is creating the correct syntax (but what do I know I'm not a programmer by any means).
Any thoughts, comments, ideas?