Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 54426 invoked from network); 2 Jun 2007 19:14:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 Jun 2007 19:14:25 -0000 Received: (qmail 444 invoked by uid 500); 2 Jun 2007 19:14:16 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 99606 invoked by uid 500); 2 Jun 2007 19:14:14 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 99595 invoked by uid 99); 2 Jun 2007 19:14:14 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 02 Jun 2007 12:14:14 -0700 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 len.popp@gmail.com designates 64.233.162.230 as permitted sender) Received: from [64.233.162.230] (HELO nz-out-0506.google.com) (64.233.162.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 02 Jun 2007 12:14:06 -0700 Received: by nz-out-0506.google.com with SMTP id i1so696536nzh for ; Sat, 02 Jun 2007 12:13:45 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=D0+gYhP9kKVc+dsX9DzfoAFwTCNyn0+IETVNOZce5Ss7RgPTWmRxf3Nh1sZRXutlAQvaYLC22PYOefjBiv8cLnp01xtEtHWU12EZXM80BpyZJmqM+QBd8qg6/QNig9b7+T38wDqaXK/GUON6Iip2wSGWl5jDUacZLgcnHpYeJug= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=oo+wLvNyLiDEyewjoxZG8uT0ISbvIniA1EKJmjANVyjaJau00lrg2CCXqg1dQFoFX9pzrafZFUrUBowpVh8zChy3dG8JJeFLdyiGQe+Ue2Ye8jbTrX1tQK6BDnFRLRn4T4fxZmvl7M7f8lJjNDJFpPxN0rq7ZiEYxErF3Yf7nvU= Received: by 10.143.38.6 with SMTP id q6mr145980wfj.1180811625295; Sat, 02 Jun 2007 12:13:45 -0700 (PDT) Received: by 10.143.10.6 with HTTP; Sat, 2 Jun 2007 12:13:45 -0700 (PDT) Message-ID: <497fac690706021213l67d25f89geca6e907f9a136ff@mail.gmail.com> Date: Sat, 2 Jun 2007 15:13:45 -0400 From: "Len Popp" To: "Tomcat Users List" Subject: Re: Missing ETag in 304 Header In-Reply-To: <3e7f52770705161222k21feeb90v19691e9e637404b2@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3e7f52770705161222k21feeb90v19691e9e637404b2@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org I submitted a fix for this, and it has been accepted for release 5.5.24 and 6.0.14. Bugzilla report: http://issues.apache.org/bugzilla/show_bug.cgi?id=42497 -- Len On 5/16/07, Joe Mun wrote: > Hi guys... so according to the HTTP 1.1 spec ( > http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html), 304 Not Modified > responses must include the ETag in the header. However, Tomcat doesn't seem > to be adding it... > > I am serving a static text file, and the header only returns: > > HTTP/1.x 304 Not Modified > Server: Apache-Coyote/1.1 > Date: Wed, etc... > > Is there a reason that the Etag is not being included? Is there a way to > configure Tomcat to include this? My company is working with a caching > solution provider, and they are complaining about the missing ETag. > > thanks. > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org