Re: Failed to decode requested authority digest

[Drake Wilson <drake@xxxxxxxxxxxx>]

Quoth Nick Mathewson <nickm@xxxxxxxxxxxxxx>, on 2010-01-14 21:49:33 -0500:
> > Jan 12 08:57:59.119 [warn] Failed to decode requested authority digest
> > 14C131%2027B6B5%20585769%2081349F%20E2A2AF%20E8A9C4.
> > Jan 14 11:40:05.641 [warn] Failed to decode requested authority digest
> > 14C131%2027B6B5%20585769%2081349F%20E2A2AF%20E8A9C4.
> 
> This looks like some kind of broken client to me.  Look at all those
> %20s in the string: that looks like http encoding of a space (" ")
> character, so somebody's program is requesting "14C131 27B6B5 585769
> 81349F E2A2AF E8A9C4" with the spaces HTTP-encoded.  Unless I'm
> mistaken, the proper format is using + signs, not spaces.

If you mean URI-encoded (or URL-encoded), which HTTP uses, then %20 is
a valid encoding of a 0x20 (ASCII space) character.  + is a secondary
convention that's used in query strings only, which can also mean a
space character.  Does the Tor directory request protocol specify
something else?  The dir-spec.txt document from Tor 0.2.1.20 doesn't
seem to be clear on how <fp> is interpreted in URIs.

   ---> Drake Wilson
***********************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxxx with
unsubscribe or-talk    in the body. http://archives.seul.org/or/talk/