Registered Member
|
Hello,
I've just get the svn revision 608866, and I found that the tracker scrape protocol is supported. But I also found a problem. The scrape url is incorrect, the info hash should be passed as "info_hash" instead as "infohash" |
Moderator
|
Euhm, this says differently :
See http://wiki.theory.org/BitTorrentSpecif ... S_Protocol It's a bit weird that an announce uses info_hash and a scrape infohash, so I can understand your confusion. |
Registered Member
|
I was confused at first, when I found that ktorrent supports scrape convention, but it didn't show me that information. Then I checked the url displayed in the log view manualy, and I found that the tracker return an information only when the info hash is sent as "info_hash".
I believe there is a mistake or some trackers respond to "infohash" and others to "info_hash". According to the Azureus Wiki http://www.azureuswiki.com/index.php/Scrape the parameter should be info_hash Here http://wiki.depthstrike.com/index.php/P2P:Programming:Trackers:PHP:Multiscrape is the same. |
Moderator
|
Don't you just love this
This could explain the following problem : http://ktorrent.org/forum/viewtopic.php?t=1087 I.e. the tracker.prq.to tracker only understands info_hash, and when we send infohash, it will just ignore the parameters it doesn't know and then send all information about all torrents, which is lot (it's the pirate bay tracker). EDIT: pending further investigation I have changed it to info_hash |
Registered users: Bing [Bot], Google [Bot], q.ignora, watchstar