From owner-freebsd-current  Thu Jul 24 16:32:41 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id QAA01632
          for current-outgoing; Thu, 24 Jul 1997 16:32:41 -0700 (PDT)
Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id QAA01624
          for <current@freebsd.org>; Thu, 24 Jul 1997 16:32:39 -0700 (PDT)
Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <52183(4)>; Thu, 24 Jul 1997 16:32:05 PDT
Received: from localhost by crevenia.parc.xerox.com with SMTP id <177512>; Thu, 24 Jul 1997 16:31:53 -0700
To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
cc: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= <ache@nagual.pp.ru>, current@freebsd.org
Subject: Re: 'fetch' error with http, fix wanted 
In-reply-to: Your message of "Thu, 24 Jul 97 07:22:13 PDT."
             <199707241422.KAA29714@khavrinen.lcs.mit.edu> 
Date: Thu, 24 Jul 1997 16:31:40 PDT
From: Bill Fenner <fenner@parc.xerox.com>
Message-Id: <97Jul24.163153pdt.177512@crevenia.parc.xerox.com>
Sender: owner-freebsd-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Garrett Wollman <wollman@khavrinen.lcs.mit.edu> wrote:
>I would say that either their TCP or their Web server is busted.

I wouldn't be surprised if it were the web server.  It's common to
want to try to detect clients that have disappeared, and there's a
common (T/TCP-breaking) assumption that if you get a read EOF then
the connection is gone and you should tear it down at the application
level.

The squid cache did this for a while, which is where I first noticed
that T/TCP requests failed.

  Bill