[Mod_gzip] "mod_gzip_send_vary=Yes" disables caching on IE? (1.3.26.1a)
mod_gzip@lists.over.net
mod_gzip@lists.over.net
Fri, 6 Dec 2002 20:03:19 EST
--part1_197.11c34460.2b22a2d7_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
In a message dated 12/6/2002 6:55:22 PM Central Standard Time, CK1@wwwtech.de
writes:
> Hello Kevin,
>
> On Fri, Dec 06, 2002 at 07:37:23PM -0500, TOKILEY@aol.com wrote:
> > Then send the bug report to SQUID ( squid-cache.org ) as well
> > SQUID behaves the same way and causes the same problems.
>
> This is not true. This *was* true for squid 2.4, and yes, I think too,
> that this is a bug. But from the changelog of 2.5:
>
> | - Responses with Vary: in the header are now cached by squid.
> | (Henrik Nordstrom).
>
> (This was the cause of my update of squid)
>
> Greetings,
> CK
>
Only 3 questions come to mind...
1. Despite what any 'changelog' comment says... how does this
REALLY work?
2. Has this version of SQUID been released to the public? Last
I heard it has NOT.
3. If it has been released... then how many years will it take before
this is still not an issue since there is no assurance that anyone
will 'upgrade' their SQUID just because a new version is out.
I think it's great that there is now at least SOME version of
SQUID that doesn't just throw any response with any
"Vary:" header onto the floor... but that's not really the issue.
Also... SQUID 2.5 still does not have full support for ETag
which means, while finally not trashing all "Vary" requests
is a step in the right direction ( finally )... it won't mean
much until there is full ETag support as well.
What's the SQUID timeframe on full ETag support
as per HTTP/1.1 specs?
Yours...
Kevin
--part1_197.11c34460.2b22a2d7_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
<HTML><FONT FACE=arial,helvetica><FONT SIZE=2>In a message dated 12/6/2002 6:55:22 PM Central Standard Time, CK1@wwwtech.de writes:<BR>
<BR>
<BR>
<BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">Hello Kevin,<BR>
<BR>
On Fri, Dec 06, 2002 at 07:37:23PM -0500, TOKILEY@aol.com wrote:<BR>
> Then send the bug report to SQUID ( squid-cache.org ) as well<BR>
> SQUID behaves the same way and causes the same problems.<BR>
<BR>
This is not true. This *was* true for squid 2.4, and yes, I think too,<BR>
that this is a bug. But from the changelog of 2.5:<BR>
<BR>
| - Responses with Vary: in the header are now cached by squid.<BR>
| (Henrik Nordstrom).<BR>
<BR>
(This was the cause of my update of squid)<BR>
<BR>
Greetings,<BR>
CK<BR>
</BLOCKQUOTE><BR>
<BR>
Only 3 questions come to mind...<BR>
<BR>
1. Despite what any 'changelog' comment says... how does this<BR>
REALLY work?<BR>
<BR>
2. Has this version of SQUID been released to the public? Last <BR>
I heard it has NOT.<BR>
<BR>
3. If it has been released... then how many years will it take before<BR>
this is still not an issue since there is no assurance that anyone<BR>
will 'upgrade' their SQUID just because a new version is out.<BR>
<BR>
I think it's great that there is now at least SOME version of<BR>
SQUID that doesn't just throw any response with any<BR>
"Vary:" header onto the floor... but that's not really the issue.<BR>
<BR>
Also... SQUID 2.5 still does not have full support for ETag<BR>
which means, while finally not trashing all "Vary" requests<BR>
is a step in the right direction ( finally )... it won't mean<BR>
much until there is full ETag support as well.<BR>
<BR>
What's the SQUID timeframe on full ETag support<BR>
as per HTTP/1.1 specs?<BR>
<BR>
Yours...<BR>
Kevin<BR>
<BR>
<BR>
</FONT></HTML>
--part1_197.11c34460.2b22a2d7_boundary--