Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 20418 invoked by uid 6000); 12 Nov 1997 17:58:02 -0000 Received: (qmail 20384 invoked by uid 24); 12 Nov 1997 17:58:01 -0000 Received: (qmail 15142 invoked from network); 12 Nov 1997 08:30:05 -0000 Received: from twinlark.arctic.org (204.62.130.91) by taz.hyperreal.org with SMTP; 12 Nov 1997 08:30:05 -0000 Received: (qmail 30701 invoked by uid 500); 12 Nov 1997 08:29:59 -0000 Date: Wed, 12 Nov 1997 00:29:59 -0800 (PST) From: Dean Gaudet To: TLOSAP Subject: Re: protocol/1399: MISE 4.0 POST, then 401 Unauth, then second POST with good uname/pwd, garbage data in logs and (sometimes) garbled request (fwd) In-Reply-To: Message-ID: Organization: Transmeta Corp. 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 But isn't the only "correct" way to read client input via your routines in http_protocol.c? get_client_block() or something like that? If so, then why don't we know how to finish things off? Dean On Tue, 11 Nov 1997, Alexei Kosut wrote: > On Tue, 11 Nov 1997, Dean Gaudet wrote: > > > See discard_request_body in http_protocol.c. ... unfortunately it looks to > > only be called by default_handler() and not die(). > > And generally, we can't. Because we have no way really of knowing if > the POST request has been read, not read, or partially read by the > module before it returns an error. > > I thought that Apache doesn't keep alive any error messages that came > from a request with an entity, for this reason. Maybe I'm remembering > incorrectly. > > -- Alexei Kosut > >