Return-Path: Delivered-To: apmail-httpd-bugs-archive@www.apache.org Received: (qmail 76202 invoked from network); 7 Jun 2006 03:58:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 7 Jun 2006 03:58:57 -0000 Received: (qmail 19631 invoked by uid 500); 7 Jun 2006 03:58:56 -0000 Delivered-To: apmail-httpd-bugs-archive@httpd.apache.org Received: (qmail 19590 invoked by uid 500); 7 Jun 2006 03:58:55 -0000 Mailing-List: contact bugs-help@httpd.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: Reply-To: "Apache HTTPD Bugs Notification List" List-Id: Delivered-To: mailing list bugs@httpd.apache.org Received: (qmail 19577 invoked by uid 99); 7 Jun 2006 03:58:55 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Jun 2006 20:58:55 -0700 X-ASF-Spam-Status: No, hits=-9.4 required=10.0 tests=ALL_TRUSTED,NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Jun 2006 20:58:55 -0700 Received: by brutus.apache.org (Postfix, from userid 33) id CA0FD7142A1; Wed, 7 Jun 2006 03:57:53 +0000 (GMT) From: bugzilla@apache.org To: bugs@httpd.apache.org Subject: DO NOT REPLY [Bug 39727] - Incorrect ETag on gzip:ed content In-Reply-To: X-Bugzilla-Reason: AssignedTo Message-Id: <20060607035753.CA0FD7142A1@brutus.apache.org> Date: Wed, 7 Jun 2006 03:57:53 +0000 (GMT) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG� RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND� INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=39727 ------- Additional Comments From hno@squid-cache.org 2006-06-07 03:57 ------- >From a protocol perspective removing the ETag is sufficient to make you compliant. If conditionals (If-xxx) anyway doesn't work right on transformed responses there is not much benefit of sending an ETag out. But if you can it's better if you send an ETag. As I said initially you don't need to compute a new etag, just adding some extra detail to the tag is fine. I.e. "638f3e-6-1b6d6340-gzip" or similar for a gzip:ed entity where the base entity had the etag "638f3e-6-1b6d6340". To HTTP the etag is just a string with the only requirement that it must be unique for each entity variants of the same URL. Actually I think adding details to the ETag may simplify many things for you as the core routines then can make quick asssssments of conditionals if it's possible to infer information about how the object had been processed from looking at the entity tag. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org For additional commands, e-mail: bugs-help@httpd.apache.org