On Thu, May 29, 2008 at 11:52 PM, John M <[EMAIL PROTECTED]> wrote:
>
> Well, I thought it was working, but alas, now it's not, let me give
> you the latest...
>
> GET /announce/?uploaded=0&compact=1&numwant=80&info_hash=%EF%BF%BDm%EF
> %BF%BDmfD%D8%9A%EF%BF%BD%EF%BF%BD%C7%86%EF%BF%BD8%EF%BF
> %BD&event=started&downloaded=0&key=yoolrpcyku&corrupt=0&peer_id=-
> TR1210-exbira35le7h&port=51413&left=0
>
> In the code:
>
> print "Debug"
> print "query string " + parse_qs(request.META['QUERY_STRING'])
> ['info_hash'][0]
> hash = parse_qs(request.META['QUERY_STRING'])['info_hash']
> [0].encode('hex')
> assert False
>
> The output from the print statements:
> Debug
> query string parseqs�m�mfDؚ��dž�8�
>
> LOCAL Variables
> c
> {'addr': '127.0.0.1', 'peer_id': u'-TR1210-exbira35le7h', 'port':
> 51413}
> hash
> 'efbfbd6defbfbd6d6644d89aefbfbdefbfbdc786efbfbd38efbfbd'
>
>
> and the debug screen snippit
>
> QUERY_STRING
> 'uploaded=0&compact=1&numwant=80&info_hash=%EF%BF%BDm%EF%BF%BDmfD%D8%9A
> %EF%BF%BD%EF%BF%BD%C7%86%EF%BF%BD8%EF%BF
> %BD&event=started&downloaded=0&key=yoolrpcyku&corrupt=0&peer_id=-
> TR1210-exbira35le7h&port=51413&left=0'
>
> Any help would be great!
>
>
What's wrong with the hash it is calculating? Lining up the %-encoded query
string with the hash produced it looks like everything is correct:
http://dpaste.com/53697/
What is the 'correct' result supposed to be? Perhaps I misunderstood
exactly how you need to interpret info_hash?
Karen
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
