Received: by taz.hyperreal.com (8.6.12/8.6.5) id JAA06138;
 Mon, 27 Nov 1995 09:20:44 -0800
Received: from ooo.lanl.gov by taz.hyperreal.com (8.6.12/8.6.5) with SMTP id
 JAA06121; Mon, 27 Nov 1995 09:20:40 -0800
Received: by ooo.lanl.gov
	(1.38.193.4/16.2) id AA22177; Mon, 27 Nov 1995 10:20:00 -0700
From: Rob Hartill <hartill@ooo.lanl.gov>
Message-Id: <9511271720.AA22177@ooo.lanl.gov>
Subject: Re: WWW Form Bug Report: "file transfer" on Linux
To: new-httpd@hyperreal.com
Date: Mon, 27 Nov 95 10:19:59 MST
In-Reply-To: <199511271812.NAA04507@luers.qosina.com>;
 from "Aram W. Mirzadeh" at Nov 27, 95 1:12 pm
X-Organization: Theoretical Division, T-8. Los Alamos National Laboratory
X-Snail: LANL Theoretical Divi' T-8, MS B285, P.O Box 1663,
 Los Alamos NM 87545
X-Marks-The-Spot: Doh !
X-Url: http://nqcd.lanl.gov/~hartill/
X-Cessive-Use-Of-Headers: check
Mailer: Elm [revision: 70.85]
Sender: owner-new-httpd@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org

 
> At 08:59 AM 11/27/95 MST, you wrote:
> > 
> >> Has anyone seen this problem?  I tried it, with 3.4 MB file, and it
> >> worked fine.  No ack sent yet.
> >
> >Timeout ?
> 
> That's what it sounds like, but he says it only happens with apache. 
> The same timeout values are working for NCSA.

NCSA timeout for send is (or was) reset after every successful send, so
Timeout there defines a maximum time which a block of output can take
to be sent.

With Apache (AFAIK), the Timeout is a "you have N seconds to send the lot"
value. So even if the transmission is slow but steady, the clock is always
counting down to zero.

The NCSA/Apache 0.6 approach is better IMO.