Context Navigation

← Previous Ticket
Next Ticket →

#3077 closed Enhancement (fixed)

No cookie support

Reported by:	saik0	Owned by:	charles
Priority:	Normal	Milestone:	2.10
Component:	libtransmission	Version:	1.92
Severity:	Normal	Keywords:	cookie, patch-needed
Cc:

Description

Some websites require authentication to download a torrent file, making them impossible for the daemon to fetch.

Attachments (1)

add_cookie_support.diff (938 bytes) - added by anville 12 years ago.: Adds cookie support for remote URL fetch

Download all attachments as: .zip

Change History (13)

comment:1 Changed 13 years ago by livings124

This seems excessive.

comment:2 follow-up: ↓ 4 Changed 13 years ago by Egil

The simplest solution is to solve the problem at the client. To download a torrent that requires authentication, you need to fint it first. If you find it via a website, you can download the torrent with your browser. What I do is to set up transmission-remote as the file type handler for torrents in Firefox. When I grab a torrent, it gets sent to the daemon behind the scene. I would rather see the devs use their precious time on other cool stuff when the solution is so easy on the client side.

comment:3 Changed 13 years ago by livings124

Keywords patch-needed added; cookies removed
Resolution set to wontfix
Status changed from new to closed

Agreed, this won't be added without a patch.

comment:4 in reply to: ↑ 2 Changed 13 years ago by saik0

Replying to Egil:

The simplest solution is to solve the problem at the client. To download a torrent that requires authentication, you need to fint it first. If you find it via a website, you can download the torrent with your browser. What I do is to set up transmission-remote as the file type handler for torrents in Firefox. When I grab a torrent, it gets sent to the daemon behind the scene. I would rather see the devs use their precious time on other cool stuff when the solution is so easy on the client side.

This makes many assumptions. If the daemon is being controlled by a handheld such as a phone it might be impossible to download the torrent file. The end user might be behind a filtering proxy, controlling a remote daemon. Also, I'm not sure if a built-in RSS downloaded is planned, but it would also make for a perfectly valid usage scenario.

I got an itch to scratch now, I'll be looking through the source this weekend.

comment:5 Changed 12 years ago by anville

This is a feature I have been wanting for a while. My favorite torrent site uses cookie authentication, and since I usually use the web interface, it limits my interactions.

I finally got around to getting the source, and found to get the basic function working is trivial, as libcurl already has support for this.

Not sure if this is the right place for this, but I attached a patch file. It just adds an extra setting for the curl opts to use a cookie file located in the app's config dir. The file is called "cookie.txt" and is standard Netscape format. I suppose GUI support could be added later, but this is beyond my ken :-)