Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 62455 invoked from network); 10 Dec 2006 15:36:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Dec 2006 15:36:58 -0000 Received: (qmail 56636 invoked by uid 500); 10 Dec 2006 15:36:58 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 56580 invoked by uid 500); 10 Dec 2006 15:36:58 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 56569 invoked by uid 99); 10 Dec 2006 15:36:58 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Dec 2006 07:36:58 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of justin.erenkrantz@gmail.com designates 66.249.92.169 as permitted sender) Received: from [66.249.92.169] (HELO ug-out-1314.google.com) (66.249.92.169) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Dec 2006 07:36:48 -0800 Received: by ug-out-1314.google.com with SMTP id 75so1076255ugb for ; Sun, 10 Dec 2006 07:36:26 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=a/lFearTBywWTRdevRhHojMX9Q1cZW2WdlGd2nMEqZSTQazdzJk3oa0FX/7vNBBRPj9TW9BZQRzM8HV6mRX8bgNC3z4Xzvn5E5xcaVbpIQLP7BdrKYxcBH2J2BoSg1dAJ/QtoQ/YcbDcO6tE9XCg+dxwtXZKlR25T868x5LxTv0= Received: by 10.78.201.2 with SMTP id y2mr2565937huf.1165764985822; Sun, 10 Dec 2006 07:36:25 -0800 (PST) Received: by 10.78.129.2 with HTTP; Sun, 10 Dec 2006 07:36:25 -0800 (PST) Message-ID: <5c902b9e0612100736ib39aaf1h236c608197e9f81@mail.gmail.com> Date: Sun, 10 Dec 2006 16:36:25 +0100 From: "Justin Erenkrantz" Sender: justin.erenkrantz@gmail.com To: dev@httpd.apache.org Subject: Re: Wrong etag sent with mod_deflate In-Reply-To: <457BFDFF.80408@apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200612061412.kB6ECwB10034@devsys.jaguNET.com> <1165531559.25753.27.camel@henriknordstrom.net> <958C9371-4A20-4765-BC90-5DD63301269A@gbiv.com> <5c902b9e0612081535n5dd4302ek7afdae87933b55e6@mail.gmail.com> <457A9F3A.4090900@apache.org> <5c902b9e0612090623g3625007dle99822aa8552ca06@mail.gmail.com> <38B6949E-DE72-49B1-8EED-8FB8E740E712@gbiv.com> <457BF4A8.4020508@apache.org> <457BFDFF.80408@apache.org> X-Google-Sender-Auth: 89af605a38683d1c X-Virus-Checked: Checked by ClamAV on apache.org On 12/10/06, Ruediger Pluem wrote: > Question: How does a client signal that it can handle TE: gzip? Also via Accept-Encoding: gzip? > Or is there another header for this? 'TE: gzip' is the header that the client sends in the request. Apache would then respond with 'Transfer-Encoding: gzip'. We would also have to tweak the chunking filter to also be able to chunk on top of that as well. (Currently, it would bail if there is any Transfer-Encoding besides identity. If a client actually supports TE: gzip, then it better also be able to handle chunking on top of that.) -- justin