Feel free to post a TCP dump of an scrape request returning peers. I'll post one proving the opposite myself:
Code:
GET /scrape?info_hash=3%82%0d%b6%dd%5eY%28%d2%3b%c8%11%bb%ac%2fJ%e9L%b8%82 HTTP/1.1
Host: torrent.ubuntu.com:6969
User-Agent: uTorrent/1850(17414)
Accept-Encoding: gzip
HTTP/1.0 200 OK
Content-Length: 119
Content-Type: text/plain
d5:filesd20:3.
..^Y(.;..../J.L..d8:completei54e10:downloadedi0e10:incompletei2e4:name28:ubuntu-8.10-desktop-i386.isoeee
Do you see any peer IPs there? I can't see any! The "files" dictionary only contains:
one key/value pair for each torrent for which there are stats
The rest of the values should be self-explanatory. "downloaded" is the amount of snatches on that torrent. "complete" is the amount of seeders. "incomplete" is the amount of leechers.
Also, let's have a look at the numwant thingy:
numwant: Optional. Number of peers that the client would like to receive from the tracker. This value is permitted to be zero.
If omitted, typically defaults to 50 peers.
My quotes are from the BitTorrent protocol specification:
http://wiki.theory.org/BitTorrentSpecification
Happy now?
Bookmarks