I figured it out, it is not that complex as I thought initially , also I thought url constructor was escaping the data. Thanks all for the help.
On Sat, Aug 13, 2011 at 9:37 AM, Veer <diggerr...@gmail.com> wrote: > Since server part expects escaped data based on rfc 1738 , I "assume" > that it will not be able to interpret the data as base64 encoding. > As per bittorrent spec , the get request to tracker must have > info_hash(20 byte sha) escaped along with others. > Is there any other way to insert query part in url without getting > escaped twice , so that I can use existing function like get-pure-port > etc. > > Thanks > > On Fri, Aug 12, 2011 at 11:08 PM, Danny Yoo <d...@cs.wpi.edu> wrote: >> The library already does some URL encoding for you, as "%" is an >> illegal character in a query string, since that's the escape character >> itself for arbitrary bytes, "%25" gets translated down to... >> >> ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; >>> (integer->char (string->number "25" 16)) >> #\% >> ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; >> >> ... that percent sign. >> >> >> Would using base64-encode (from the net/base64 library) work for you? >> You can take your bytes and feed them through base64-encode; the >> result should be something that can be a part of URLs. >> > _________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/users
