Delivery-Date: Wed, 02 Dec 2015 22:54:39 -0500
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_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,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 B8FFB1E01AC;
	Wed,  2 Dec 2015 22:54:37 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 2CDDA37053;
	Thu,  3 Dec 2015 03:54:32 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id A216E3704F
 for <tor-talk@lists.torproject.org>; Thu,  3 Dec 2015 03:54:28 +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 X9o-ikvC3YQg for <tor-talk@lists.torproject.org>;
 Thu,  3 Dec 2015 03:54:28 +0000 (UTC)
Received: from mail-yk0-x22d.google.com (mail-yk0-x22d.google.com
 [IPv6:2607:f8b0:4002:c07::22d])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 7F0D23703F
 for <tor-talk@lists.torproject.org>; Thu,  3 Dec 2015 03:54:28 +0000 (UTC)
Received: by ykdv3 with SMTP id v3so72293550ykd.0
 for <tor-talk@lists.torproject.org>; Wed, 02 Dec 2015 19:54:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=peeh5xo/NgX1Ow6SuqwaOw9aD/AzynhZ8lMH7znS2Jk=;
 b=ZoZZv0Lw0p3RhofR0wCm2xPp6GrXmFOM+P6ehG0jN+29qTbD7voweVN5v4aWZ+SW54
 mxCzQtbSHQjuLLODd+w7G9cY+r3GVnNm0u/S61WE9XXCkuDYFb6eXZf7KImueNAYpQFk
 1pJ2kVJAnMO+2/u8GNlXeOG9+muOzVQGrf6V7sdcXY/3gW511JKnB5FOCOlwxBIwIhh+
 Bw3DLjvSrREugx9ONDgYEOGWg7UdUrmax+aJj9ucXHCDMhgOHCAWDBh8aeLpfBffwhOh
 hejC6HPCdOLmxloiMwbeYr2Dh0Zy8zyn2vcC/W5TNw/nEaeR3wGBiP3c/10un2n8W6cg
 A1yQ==
MIME-Version: 1.0
X-Received: by 10.129.156.215 with SMTP id t206mr4871037ywg.152.1449114866086; 
 Wed, 02 Dec 2015 19:54:26 -0800 (PST)
Received: by 10.129.74.4 with HTTP; Wed, 2 Dec 2015 19:54:26 -0800 (PST)
Date: Wed, 2 Dec 2015 22:54:26 -0500
Message-ID: <CAB7TAMk4sVh+6Ytxt5Xd7O+1VxsfVLxyQdEcAaayu4PjwYfSjg@mail.gmail.com>
From: Allen <allenpmd@gmail.com>
To: tor-talk@lists.torproject.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [tor-talk] regression in torproxy 2.7.4?
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>

I have a webservice that runs as a tor hidden service.  The client connects
to torproxy using a random socks4 username (which results in fresh circuit)
and sends a short string to the server.  The server sends a response from a
few bytes to a few kilobytes in size, then gracefully closes the
connection.  This is roughly equivalent to accessing a website with
"keep-alive" turned off.

This ran like a champ under torproxy 2.6.10.  It could run it for days with
no unexpected behavior.

With torproxy 2.7.4 however, the client is seeing a partial response
roughly every 1000 requests.  Sometimes it looks to the client like the
server closed the connection without sending any data, and sometimes it
looks like only half the data gets there (which might be roughly 500 bytes
or one cell worth, although I haven't measured it exactly).

I'm not sure what to make of this.  Any network protocol has the potential
for transmission errors and the client and server should be able to handle
them, but I'm still wondering if 2.7.4 might have a regression that
sometimes leads it to not forward all pending data before a connection is
gracefully closed.

If I back off to 2.6.10, I still see these partial responses although less
frequently.  That could be because routers in the circuit are running
2.7.4.  Or maybe I just got lucky before with 2.6.10 and it had the
potential for the same behavior but I just never saw it.

Is anyone else seeing partial page loads or similar behavior with 2.7.4?
Any other thoughts on what I'm seeing?

Thanks.
-- 
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

