Received: (from majordom@localhost) by hyperreal.com (8.8.4/8.8.4) id QAA27280; Mon, 21 Apr 1997 16:10:53 -0700 (PDT) Received: from paris.ics.uci.edu (mmdf@paris.ics.uci.edu [128.195.1.50]) by hyperreal.com (8.8.4/8.8.4) with SMTP id QAA27269 for ; Mon, 21 Apr 1997 16:10:48 -0700 (PDT) Received: from kiwi.ics.uci.edu by paris.ics.uci.edu id aa25187; 21 Apr 97 16:06 PDT To: new-httpd@apache.org Subject: Re: [PATCH] Handle timeouts in buffers as well as connection In-reply-to: Your message of "Mon, 21 Apr 1997 16:55:05 CDT." <199704212155.QAA06686@sierra.zyzzyva.com> Date: Mon, 21 Apr 1997 16:06:25 -0700 From: "Roy T. Fielding" Message-ID: <9704211606.aa25187@paris.ics.uci.edu> Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org >The actual data transfer is not any slower, but Netscape seems to >be reporting it as such. I'm not sure what Netscape bases transfer >rate calculations on. I'm assuming a value in the Content-Length. Weird. One thing I did notice, since Dean's buffering improvements, is that a slow CGI script won't send *anything* until it either completes or fills an 8KB (IOBUFSIZE) in send_fd. This is the one area that I wouldn't mind a bflush between the header fields and the body, but I don't run a site that depends on fast CGI buffering. Hmmm, I wonder if your Content-Length just happens to be at the 256-257 bytes? .....Roy