Torrage not working with web interface

[hmphargh]

As I'm developing my Greasemonkey script, I've run into an issue with torrage torrent links.
Here is an example of a Slackware 12.2 torrent:

Code: Select all

http://torrage.com/torrent/640FE84C613C17F663551D218689A64E8AEBEABE.torrent

I cannot seem to get Transmission to accept them through RPC calls or the standard web interface, but I have no problem when I add the torrent via URL on the client itself. I though it might be a redirect or rewrite rule causing problems on the server side, but I am able to successfully use wget and curl -C - -O to download the torrents so I don't think that is the issue. Can anyone shed some light on what the issue might be?

[Jordan]

It seems to be some problem with the way torrage.com's webserver is serving up the file.

For example if I load "elinks http://torrage.com/torrent/640FE84C613C ... BE.torrent" and click on "display", I see the usual "d8:announce" at the front of the file. And if the use File > Save in elinks, the resulting file is one that works in Transmission.

On the other hand if I use "wget http://torrage.com/torrent/640FE84C613C ... BE.torrent" and then load up the results in an editor, the contents are garbage.

[hmphargh]

After reading the site http://www.torrage.com, it says that the torrents are gzipped. I have verified by unzipping one, it starts out with d8:announce. The strange thing is that the desktop client seems to handle the gzipped files and links fine, but the web front end chokes on them. Is there a reason the web client can't handle gzipped torrents but the desktop client can?

[Jordan]

What version of Transmission are you running, and which GUI are you using when you refer to "the desktop client"?

[hmphargh]

I'm running Transmission for Mac 1.83 (10400), and I'm referring to the built in web server when I talk about the web front end, sorry I wasn't clear about that.