On Thu, Jan 14, 2010 at 9:12 AM, Olaf Selke <olaf.se...@blutmagie.de> wrote: > Olaf Selke wrote: >> >> since a couple of days tor logs an error condition about every 32 hours. >> Even looking at the code I don't really understand the cause. >> >> Jan 07 00:56:46.100 [warn] Failed to decode requested authority digest >> 14C131%2027B6B5%20585769%2081349F%20E2A2AF%20E8A9C4. >> Jan 08 09:48:38.437 [warn] Failed to decode requested authority digest >> 14C131%2027B6B5%20585769%2081349F%20E2A2AF%20E8A9C4. >> Jan 09 17:35:39.847 [warn] Failed to decode requested authority digest >> 14C131%2027B6B5%20585769%2081349F%20E2A2AF%20E8A9C4. >> Jan 11 01:05:58.288 [warn] Failed to decode requested authority digest >> 14C131%2027B6B5%20585769%2081349F%20E2A2AF%20E8A9C4. > > Hi folks, > > still getting these errors. Is there anybody out there knowing what this > means? > > 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. It's also possible that they've got an HTTP proxy that is re-encoding their request for some reason. Either way, it's nothing to worry about on your side. *********************************************************************** To unsubscribe, send an e-mail to majord...@torproject.org with unsubscribe or-talk in the body. http://archives.seul.org/or/talk/