Delivery-Date: Thu, 09 Jul 2015 03:56:26 -0400
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.1 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	RCVD_IN_DNSWL_MED,T_DKIM_INVALID,T_RP_MATCHES_RCVD autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 885351E0323;
	Thu,  9 Jul 2015 03:56:24 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 13ADF36559;
	Thu,  9 Jul 2015 07:56:20 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id A0E953651C
 for <tor-talk@lists.torproject.org>; Thu,  9 Jul 2015 07:56:16 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id b0giVFC51VIP for <tor-talk@lists.torproject.org>;
 Thu,  9 Jul 2015 07:56:16 +0000 (UTC)
Received: from gerbil.it (unknown [107.6.175.158])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 7492836224
 for <tor-talk@lists.torproject.org>; Thu,  9 Jul 2015 07:56:16 +0000 (UTC)
Received: from mailpile.local (localhost.localdomain [127.0.0.1])
 (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by gerbil.it (Postfix) with ESMTPSA id DC6881C29B92;
 Thu,  9 Jul 2015 02:56:10 -0500 (CDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gerbil.it; s=default;
 t=1436428573; bh=f2XuMO5NwC8aap/Gb8wK8rKZbmRjUEw/A1kJSLiXcTM=;
 h=Subject:From:To:In-Reply-To:References:Date;
 b=pO2u5ItLg+Ungkrkjhywtn2+6EkmJcShgs3aF3o80tlSA2y+B2BxCPujkvx1Nv5/u
 aOvrrxdNEt05q/aMKUC/dooz2Q6XN2lgKEBZut4UXiOo6JFYW6LB8ePKGdY4sHXJ0z
 KDpnk9QQAKOF4eCHaDsQ3xpT9EiKbALLzZ0Bqjms=
MIME-Version: 1.0
From: Ben <ben@gerbil.it>
To: "tor-talk@lists.torproject.org" <tor-talk@lists.torproject.org>
In-Reply-To: <559E10D2.7020205@copper.net>
References: <559E10D2.7020205@copper.net>
Date: Thu, 09 Jul 2015 07:17:07 -0000
Message-Id: <20150709071638-728-33413-mailpile@mailpile-home>
OpenPGP: id=1F9164D62373F057DF3971567F57C6686ACBCC6D; preference=signencrypt
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] OnionBalance Hidden Service has over 1 million
 successful hits in just 3 days
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>


> Also, Thomas, I am wondering if you can explain what the 304 (Not
Modified), 404 (Not Found), and 403 (Forbidden) codes were caused by.

I'd assume the 304 was probably someone pressing refresh in a browser,
it'll cause a conditional get (either based on Etag or last-modified)
which would result in a 304. IIRC it's also possible to have wget/curl
do revalidations as well, though not sure why you'd want to in this
instance.

I wouldn't be surprised if the 404's were also a browser attempting to
get a favicon.


Jim <jimmymac@copper.net> wrote:
> Ben wrote:
> > I forgot to tell it to add a timestamp, so comparison against your logs
> > would be nigh on impossible - have set the same script running with
> > timestamps added, will keep an eye to see whether any failed connections
> > have been logged.
> > 
> > I do, however, have some entries in my tor client logs
> > 
> > Jul 08 09:03:55.000 [notice] Rend stream is 120 seconds late. Giving up
> > on address '[scrubbed].onion'.
> 
> For various reasons I have only been able to make a few connections, but
> they have been more than 10 minutes apart so, as I understand it, they
> should all have established new circuits.  This was scripted using wget.
> I have had over 40 successes with one failure, logged as follows (I
> have adjusted the time to UTC):
> 
> Jul  9 05:10:23 host Tor[15947]: Tried for 120 seconds to get a
> connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc)
> 
> Following this failure I have had some successes. (Initially I thought
> maybe the test site had been shut down.)
> 
> Also, Thomas, I am wondering if you can explain what the 304 (Not
> Modified), 404 (Not Found), and 403 (Forbidden) codes were caused by.  I
> suppose for 404 somebody could have requested a non-existent page on the
> site, but the other two have me baffled.
> 
> Jim
> 
> 
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

