From owner-freebsd-current Wed Jul 23 14:27:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA15702 for current-outgoing; Wed, 23 Jul 1997 14:27:53 -0700 (PDT) Received: from lsd.relcom.eu.net (lsd.relcom.eu.net [193.124.23.23]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA15693 for ; Wed, 23 Jul 1997 14:27:49 -0700 (PDT) Received: (from ache@localhost) by lsd.relcom.eu.net (8.8.6/8.8.5) id BAA04047; Thu, 24 Jul 1997 01:27:39 +0400 (MSD) Date: Thu, 24 Jul 1997 01:27:39 +0400 (MSD) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= X-Sender: ache@lsd.relcom.eu.net To: Garrett Wollman cc: FreeBSD-current Subject: Re: 'fetch' error with http, fix wanted In-Reply-To: <199707232105.RAA26899@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 23 Jul 1997, Garrett Wollman wrote: > < said: > > > This command > > fetch http://www.lothlorien.net/~squirrel/giger/art/Necronomicon_I.jpg > > > always says "connection reset by peer" in the middle of file transfer, > > meanwhile, new -current ftp or lynx do it sucessfully! > > Does anybody knows sockets enough to fix it? > > I would make a wild guess and suggest that it's likely a TCP bug on > their end, but without being able to get a tcpdump trace of it I can't > be certain. (It could, of course, also be a TCP bug on our end.) > But why ftp or lynx always works, if it is TCP bug? They show -stalled- state sometimes and I think fetch treat -stalled- as resetting by peer... I see the same behaviour already 4 times in the past, but forget other URLs. -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/