[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: Failed to decode requested authority digest
- To: or-talk@xxxxxxxxxxxxx
- Subject: Re: Failed to decode requested authority digest
- From: Nick Mathewson <nickm@xxxxxxxxxxxxxx>
- Date: Thu, 14 Jan 2010 21:49:33 -0500
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-talk-outgoing@xxxxxxxx
- Delivered-to: or-talk@xxxxxxxx
- Delivery-date: Thu, 14 Jan 2010 21:49:55 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=npCvveatrue9DiHftt1t+1NZLI86BdshoXPWc5gWY7Y=; b=nk47J7HY30oYXYBER4RM6wv7+l0C6oT3T2L6O7utiemByzCwrGuRmdlqGgeXQjN6Wy kIOZO89G6euogx+6yPrxePoK4afglbW+fyb4dW0kdpObd++6+xyN7CRfo9M2fJHZCOaZ OpkpdMZw+ZEnUWpkmF5T91Tq7NXLlzsblzjx8=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=ntDQUMI1sjgnWVhliOJo9hG0kZPSw9/JMU9VWV3oDZ69Alu4Vx95fFGl91uPAOi+Lq VkwNONk/l2/6UOphy+49xz0CSbMt6n9od9yLras1DNCBQ7YQk1//T5Cxkr0n80XMHMc5 r5iKyptLZY++zaVCeywrWmaUlLRWo6rFNAHAs=
- In-reply-to: <4B4F2650.2070805@xxxxxxxxxxxx>
- References: <4B4B8AF5.1010108@xxxxxxxxxxxx> <4B4F2650.2070805@xxxxxxxxxxxx>
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
On Thu, Jan 14, 2010 at 9:12 AM, Olaf Selke <olaf.selke@xxxxxxxxxxxx> 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 majordomo@xxxxxxxxxxxxxx with
unsubscribe or-talk in the body. http://archives.seul.org/or/talk/