Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (athena.apache.org: domain of jaltuve@gmail.com designates
 66.249.92.168 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=received:message-id:date:from:to:subject:mime-version:content-type;
        b=x04VA7ZK1smt17BzFj97CPz6SGcxUwku/fK7XmPt+ki8nOGk+3EhoZqbos5T3QIfODFRbB6YBHS5tp0GBqqYIjY+r2Y8DcRa+7Wi0Id6HG5NgZxTlbyyc5K4iVoml59oqGvi4tzGD8t7Z59s+NzIiP6JmrZmUC99YydTwEVOHrM=
Message-ID: <24e094360711241412o71fc4dadne81c37b2d675023e@mail.gmail.com>
Date: Sat, 24 Nov 2007 17:12:39 -0500
From: "Jesus Altuve" <jaltuve@gmail.com>
To: dev@httpd.apache.org
Subject: mod_cache, Vary Header and (gzip,deflate) vs (gzip, deflate)
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_34417_18412791.1195942359602"

------=_Part_34417_18412791.1195942359602
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi!

I've noticed that Internet Explorer (6) Accept-Encoding request header is
sent with spaces
(e.g gzip, deflate), so, if a Vary: Accept-Encoding is present when caching
responses there will be a cache miss, even though the request should be
served from cache.

So, the workaround is to do an early processing for RequestHeader and modify
it removing spaces. My question is:

should mod_cache match Vary headers 'exactly' as they are or would it be
advisable to simply 'remove spaces' from it and then match so browser bugs
such as this won't cause cache misses?

------=_Part_34417_18412791.1195942359602
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div>Hi!</div>
<div>&nbsp;</div>
<div>I&#39;ve noticed that Internet Explorer (6)&nbsp;Accept-Encoding request header is sent with spaces </div>
<div>(e.g gzip, deflate), so, if a Vary: Accept-Encoding is present when caching responses there will be a cache miss, even though the request should be served from cache.</div>
<div>&nbsp;</div>
<div>So, the workaround is to do an early processing for RequestHeader and modify it removing spaces. My question is:</div>
<div>&nbsp;</div>
<div>should mod_cache match Vary headers &#39;exactly&#39; as they are or would it be advisable to simply &#39;remove spaces&#39; from it and then match so browser bugs such as this won&#39;t cause cache misses?</div>
<div>&nbsp;</div>
<div>&nbsp;</div>

------=_Part_34417_18412791.1195942359602--