Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 76809 invoked by uid 500); 3 Nov 2000 01:36:37 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 76793 invoked from network); 3 Nov 2000 01:36:33 -0000 X-Authentication-Warning: adsl-77-241-65.rdu.bellsouth.net: trawick set sender to trawickj@bellsouth.net using -f Sender: trawick@bellsouth.net To: new-httpd@apache.org Subject: Re: cvs commit: apache-2.0/src/main http_core.c http_protocol.c References: From: Jeff Trawick Date: 02 Nov 2000 20:33:39 -0500 In-Reply-To: Jeff Trawick's message of "02 Nov 2000 20:02:30 -0500" Message-ID: Lines: 30 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Jeff Trawick writes: > Sascha Schumann writes: > > > I don't see anything particularly which would help me to make > > the PHP module work again. > > > > Maybe our understanding of the term "streaming" differs. > > Yep... you want the content to go the client ASAP and the filter (for > HTTP 1.0 when there isn't a content length) wants to hold onto the > content to calculate the length... > > Comment-out the ap_add_filter() for now... I don't have time to > code/commit even that much at the moment... feel free to do so > yourself. I think the fix is to leave content length filter in there, but if it sees a flush bucket prior to EOS it should disable itself and let everything flow as it comes. A module has to do a flush to let the content flow to the client ASAP so we can use that trigger to know what to do. Does that sound reasonable? -- Jeff Trawick | trawick@ibm.net | PGP public key at web site: http://www.geocities.com/SiliconValley/Park/9289/ Born in Roswell... married an alien...