Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 25280 invoked by uid 6000); 29 Jun 1998 20:59:05 -0000 Received: (qmail 25273 invoked from network); 29 Jun 1998 20:59:04 -0000 Received: from epic15.stanford.edu (171.64.15.48) by taz.hyperreal.org with SMTP; 29 Jun 1998 20:59:04 -0000 Received: (from akosut@localhost) by epic15.Stanford.EDU (8.8.8/8.8.4) id NAA04478; Mon, 29 Jun 1998 13:58:58 -0700 (PDT) Date: Mon, 29 Jun 1998 13:58:58 -0700 (PDT) From: Alexei Kosut To: new-httpd@apache.org Subject: Re: ap_setup_client_block() perversity In-Reply-To: <3597FD40.2E23AE8A@algroup.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org On Mon, 29 Jun 1998, Ben Laurie wrote: > Ah, I get it. You mean if we get T-E and no C-L, we say "give me a C-L > (instead of a T-E)". If we get both, we say "sod off". (only in the case Yep, that's about the size of it. > where someone wants to say REQUEST_CHUNKED_ERROR, of course, which leads > me on to, err, why would anyone do that?). Thankyou. If they need a content lenght. mod_cgi uses REQUEST_CHUNKED_ERROR, for example, because CGI/1.1 specifies that the CONTENT_LENGTH environment variable must be available for requests with an entity (that's how the CGI spec defines the amount of client data to read, rather than something sensible like reading until EOF). Certainly, anyone writing a brand-new protocol today should properly deal with chunked requests, but unfortunately we're stuck with legacy stuff that this code deals with. -- Alexei Kosut Stanford University, Class of 2001 * Apache *