[bittorrent] encoding issue

Harold Feit dwknight at depthstrike.com
Tue Aug 7 22:49:23 EDT 2007

Both are valid actually. You should not be using the urlencoded infohash
to identify the torrent. Use a decoded one (20 bytes).

Dazen D wrote:
> Hi, i'm facing a strange problem trying to implement a tracker service
> using java servlet technology (with Tomcat 6.0.13). When a typical
> announce request arrives in the server, the info_hash parameter that i
> get is:
> info_hash=j%ad%5c%1d%01i%25%c4%5e%ee%06%de%a9%95%3b%f5H%d6%91b
> In fact it should be :
> %6a%ad%5c%1d%01%69%25%c4%5e%ee%06%de%a9%95%3b%f5%48%d6%91%62
> but apparently some of the hex are arriving incorrectly, like 'j'
> instead of '%6a'. When i send a similar request via browser like
> http://localhost?info_hash=%6a%ad%5c%1d%01%69%25%c4%5e%ee%06%de%a9%95%3b%f5%48%d6%91%62
> it works properly. I tested using uTorrent and Azureus and the problem
> was the same. Any ideas about it? thanks a lot.
> dazen
> _______________________________________________
> BitTorrent mailing list
> BitTorrent at lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/bittorrent

More information about the BitTorrent mailing list