Opened 11 years ago

Closed 6 years ago

#3410 closed Enhancement (invalid)

Add abbility to download files over HTTP (and maybe also FTP)

Reported by: bugmenot Owned by:
Priority: Normal Milestone:
Component: Transmission Version: 2.01
Severity: Normal Keywords: http ftp download remote
Cc: bugmenot

Description

There is already option to download *.torrent file specified by URL, so why we can't also download files using HTTP just like we are downloading them from torrents?

i mostly use a torrents, but sometimes i need to transfer some big file over HTTP (or FTP in minor cases). in such case i need to SSH to my server, start screen, start wget, detach from screen and logout from SSH again - then i have to attach to screen again everytime i want to check how far the downloading have gone. i guess it can be quite simple to enable downloading files from remote webserver using transmission. so i will be able to just paste URL of desired file to web client and check some checkbox like "Download over HTTP" which will prevent transmission to treat URL as *.torrent file and will make it just download it instead (while showing progress bar and speed like for torrents).

I know that transmission is primary aimed to downloading torrents, but torrents are using some HTTP stuff too, so i guess that most of HTTP client code is already there. please think about it...

Change History (16)

comment:1 Changed 11 years ago by charles

  • Milestone 2.10 deleted
  • Resolution set to invalid
  • Status changed from new to closed

Why reinvent the wheel?

There are already several software packages out there dedicated to serving files via http or ftp. They are already focused and well-versed in http/ftp security and common features. IMO it makes more sense to use Transmission in concert with Samba or your http or ftp daemon of choice.

If Transmission were to add this feature, there would be no end to the feature requests and security issues it would raise.

comment:2 Changed 11 years ago by bugmenot

  • Resolution invalid deleted
  • Status changed from closed to reopened

have you even read the bug before closing it? this is not about serving! i just think that transmission can be able to download files from HTTP just like "wget -c" does, because it will be very user friendly...

Last edited 11 years ago by bugmenot (previous) (diff)

comment:3 follow-up: Changed 11 years ago by charles

  • Resolution set to invalid
  • Status changed from reopened to closed

Ah, I apologize. I misunderstood the ticket. Thank you for reopening the ticket and correcting my mistake. :)

Okay, this is even more certain ground. With the exception of webseeds, over my dead body will Transmission be an http or ftp client. Transmission is a BitTorrent? client, not a generic download manager.

comment:4 Changed 11 years ago by hullamospapagaj

Aww! That would be awesome!

comment:5 Changed 11 years ago by bugmenot

IMHO it's not too hard to implement especialy when there is probably already everything needed to implement such feature. i know that transmission is bittorent only, but i think this could be quite usefull. transmission already can download files over HTTP so why not download user specified files too? there will be absolutely no pain for having such feature...

if you need webseeds so much, you can generate webseed torrent for desired URL before downloading and download it instead of "just" downloading the file directly :-)

comment:6 Changed 11 years ago by bugmenot

  • Resolution invalid deleted
  • Status changed from closed to reopened

well and what about creating some simple plugin API, so users will be able to add their own protocols? eg.:

...
download *d = new_download("url");
start_download(d);
pause_download(d);
struct download_info *di = get_download_info(d);
...

seems more nice to you?

comment:7 Changed 11 years ago by charles

  • Resolution set to invalid
  • Status changed from reopened to closed

Not really. They work it would take to add such a plugin infrastructure is actually probably more work than just adding the code directly, since we already use libcurl for tracker announces.

The issue is more about where the development team needs to be spending its time, and this isn't the place.

comment:8 Changed 11 years ago by bugmenot

so patches are welcome. right?

comment:9 Changed 11 years ago by livings124

Not for this. This functionality will not be added. Please, feel free to submit patches for other features, however.

comment:10 Changed 8 years ago by mudd1

Will the advent of Metalink change your mind here?

I'd use aria2c but it doesn't have the web interface and the daemon architecture that transmission does. So there really is no reasonable workflow with any software I know for getting a torrent seeded on a dedicated machine when the data still resides mainly on HTTP servers.

comment:11 Changed 7 years ago by JasonPAtkins

I also agree that this would be a really handy feature. I understand that transmission is a torrent client, but why can't it be a download manager?

For every user that takes the time to create an account and comment here, there are hundreds of others that would like the functionality but don't comment.

The web front end is really handy, and now that lots of people are using it on routers and other embedded devices to do low power downloading, why restrict them to just torrents?

Transmission is already downloading .torrent files anyway, right? Just take away the rule that says that it can only download .torrent, and then if the file is anything else, download it and don't treat it as a torrent. Easy.

I think I understand your resistance to diluting the pure function of Transmission as a torrent client - but if it can be more useful to more people (and with very little development time), why not?

comment:12 in reply to: ↑ 3 Changed 7 years ago by bubulina

Replying to charles:

Ah, I apologize. I misunderstood the ticket. Thank you for reopening the ticket and correcting my mistake. :)

Okay, this is even more certain ground. With the exception of webseeds, over my dead body will Transmission be an http or ftp client. Transmission is a BitTorrent? client, not a generic download manager.

comment:13 Changed 6 years ago by leandroong

Aria2 can download http and torrent, I don't see why it should not be included as well in the transmission capability. At the moment, I have been using aria2 and transmission installed from my main router. Nicer if I can eliminate aria2 and just concentrate on transmission. Reference for aria2, https://github.com/ziahamza/webui-aria2

comment:14 Changed 6 years ago by xstream

  • Resolution invalid deleted
  • Status changed from closed to reopened

This would be a great addition to Transmission. Many users have Transmission running on small appliances (routers etc.) or servers and just send links to it and have them download in the background or over night. If this could be done with "normal" http downloads it would be great.
Integrating this feature into Transmission makes sense because running a second service with a second web front end and so on is just inefficient and also not very user friendly.

comment:15 Changed 6 years ago by leandroong

This should have been included long time ago. ATM there is aria2 web GUI that can perform this and torrent too. There is little need for me to have this feature but I would like to post link were aria2 source corde can be downloaded and perhaps incorporated here, http://sourceforge.net/projects/aria2/files/stable/

comment:16 Changed 6 years ago by mike.dld

  • Resolution set to invalid
  • Status changed from reopened to closed

As already stated by @charles and @livings124, this will not be added, even with ready-made patch. You are free to use Aria2 or whatever else program if you find it better suited for your needs.

Note: See TracTickets for help on using tickets.