-log_type = LOG_TCP_MISS;
clientProcessMiss(http);
}
-Original Message-
From: Odhiambo Washington [mailto:[EMAIL PROTECTED]
Sent: Monday, October 10, 2005 10:41 PM
To: squid-users@squid-cache.org
Subject: Re: [squid-users] 302 response becomes not cacheable
On Mon, 10 Oct 2005, Chris Fong wrote:
I am currently using squid 2.5.STABLE9. I noticed that if my request
has the if-modified-since header, server's 302 response becomes no
longer cacheable.
There is a lot odd things going on with cacheable 302 replies, not only
this. 302 is somewhat
On Tue, 11 Oct 2005, Chris Fong wrote:
Thanks for the suggestions. I have checked out STABLE11
source code and I believe the behavior is the same.
It is the same. Has been like this since at least 1998 and the question
has not come up until now.
So, do you think this is a bug?
Squid
AM
To: Chris Fong
Cc: squid-users@squid-cache.org
Subject: Re: [squid-users] 302 response becomes not cacheable with
if-modified-since header?
On Mon, 10 Oct 2005, Chris Fong wrote:
I am currently using squid 2.5.STABLE9. I noticed that if
my request
has the if-modified-since
On Tue, 11 Oct 2005, Chris Fong wrote:
Thanks for the answer. Is it true that once 302 becomes
cacheable, the 304 response (if-modified-since = last-modified)
will become cacheable as well?
No. The two are completely different issues.
304 is cacheable today, but only if the object as such
-Original Message-
From: Henrik Nordstrom [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 11, 2005 1:35 PM
To: Chris Fong
Cc: Henrik Nordstrom; squid-users@squid-cache.org
Subject: RE: [squid-users] 302 response becomes not cacheable with
if-modified-since header?
On Tue, 11 Oct 2005
Hi,
I am currently using squid 2.5.STABLE9. I noticed that if my request has the
if-modified-since header, server's 302 response becomes no longer cacheable.
However, if I take out that header, the 302 response becomes cacheable again.
However, if the response is 200 instead of 302, even
* On 10/10/05 20:09 -0700, Chris Fong wrote:
Hi,
I am currently using squid 2.5.STABLE9. I noticed that if my request has
the if-modified-since header, server's 302 response becomes no longer
cacheable. However, if I take out that header, the 302 response
becomes cacheable again. However,
