From owner-freebsd-current Wed Jul 23 17:00:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA24411 for current-outgoing; Wed, 23 Jul 1997 17:00:47 -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 RAA24401 for ; Wed, 23 Jul 1997 17:00:41 -0700 (PDT) Received: (from ache@localhost) by lsd.relcom.eu.net (8.8.6/8.8.5) id EAA07000; Thu, 24 Jul 1997 04:00:34 +0400 (MSD) Date: Thu, 24 Jul 1997 04:00:33 +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: <199707232353.TAA27367@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: > > Forget to mention that the server on other side (from my bug report) > > is Apache 1.2.0 which is 1.1-conformant and send this 'chunked' output > > which fetch can't handle (it cause 'connection reset by peer' for it). > > No, it has nothing whatsoever to do with your problem. If it did, > `fetch' would be outputting a warning message saying so. UTSL. You are right, nothing changed (I still got error in the middle), if I replace 1.1 with 1.0... So, it is not TCP extensions bug and not 1.1 bug... Any ideas? -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/