I just received a torrent file that rtorrent 0.6.4 couldn't use
it. It looked like this (output from tornado's
btshowmetainfo.py):
announce url..:
http://www.xxxx.com/announce.php?passkey=1410663e62dfdd37970e7387aa2e72e1
announce-list.:
http://www.xxxx.com/announce.php,http://www.xxxx.com/redir.php
domain name and passkey changed from real, of course.
rtorrent made a tracker list consisting of:
http://www.xxxx.com/announce.php
http://www.xxxx.com/redir.php
And those didn't work because the tracker wants a passkey.
It didn't use the value from "announce url" at all, and it
didn't propagate the "?passkey=1410663e62dfdd37970e7387aa2e72e1"
to the two trackers in the announce-list, and therefore was
given an error from the tracker. Other clients seem to be using
this torrent file fine. I used tornado's btreannounce.py program
to change the torrent to have the announce url but no announce-list
and then it worked with rtorrent as you'd expect.
I don't know if it *should* use the arguments from the announce
url with other entries in the "announce-list" or not, or if it
should include the "announce url" in the list of trackers as well
as the two from the "announce-list", but either one of those
things would have let this torrent work unaltered. My best guess
from the help output of btreannounce is that rtorrent is doing
the right thing by ignoring the "announce" when the
"announce-list" is present, and also I don't think it is safe or
good to take the http arguments from the announce url and add
them to the urls from the announce-list.
Possibly it would be within spec to fall back to the announce
value when all values from the announce-list fail to work?
--
Charles Clark | [EMAIL PROTECTED]
_______________________________________________
Libtorrent-devel mailing list
[email protected]
http://rakshasa.no/mailman/listinfo/libtorrent-devel
