Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 94065 invoked from network); 13 Sep 2008 14:54:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 13 Sep 2008 14:54:26 -0000 Received: (qmail 56979 invoked by uid 500); 13 Sep 2008 14:54:13 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 56964 invoked by uid 500); 13 Sep 2008 14:54:13 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 56953 invoked by uid 99); 13 Sep 2008 14:54:13 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 13 Sep 2008 07:54:13 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [80.229.52.226] (HELO grimnir.webthing.com) (80.229.52.226) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 13 Sep 2008 14:53:13 +0000 Received: from grimnir (localhost [127.0.0.1]) by grimnir.webthing.com (Postfix) with ESMTP id 9F5512135 for ; Sat, 13 Sep 2008 15:53:12 +0100 (BST) Date: Sat, 13 Sep 2008 15:53:10 +0100 From: Nick Kew To: users@httpd.apache.org Message-ID: <20080913155310.2953ef26@grimnir> In-Reply-To: <48CBC7E3.5030204@eggplant.ws> References: <48CBC7E3.5030204@eggplant.ws> Organization: WebThing X-Mailer: Sylpheed-Claws 2.5.0-rc3 (GTK+ 2.10.6; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Subject: Re: [users@httpd] Chunked + Gzip On Sat, 13 Sep 2008 11:02:11 -0300 Michael Caplan wrote: > 1. the gzip content encoding happens on the entire body before it is > chunked. > 2. the ungzipping happens on the entire body after it is dechunked. Exactly. > If I got this right (which I don't think I do), the web server would > need to first dechunk data produced from a dynamic source (PHP) > before it can apply the gzip content encoding. Why would PHP want to concern itself with chunked encoding? That's the business of the webserver, not the application. > Likewise, on the client end, it would only be able to begin > interpreting HTML following receiving the entire chucked payload, > dechunk it, and then ungzip it. You don't need the entire contents to start displaying it. Unless you rely on something whole-document, like parsing to a DOM. > But, that seems contrary to what Apache + mod_deflate actually does, What seems contrary? Read up on the apache filter chain. That's the basis for ordering different encodings, and indeed other transformations from content manipulation like SSI or XSLT through to SSL. -- Nick Kew Application Development with Apache - the Apache Modules Book http://www.apachetutor.org/ --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org " from the digest: users-digest-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org