2006/5/3, Henrik Nordstrom <[EMAIL PROTECTED]>:
ons 2006-05-03 klockan 12:42 +0200 skrev Aurélien Bras:
> TCP_REFRESH_ mean my object is STALE and Squid need to verify on
> public serveur. HIT mean the object is still good and MISS it isn't.
> So, with a miss i need to dowload the file.
Well, not really. A /304 is a "Not modified" message where only headers
exchanged verifying that the object hasn't changes, no file content.
> With no_cache deny BACK :
> TCP_REFRESH_HIT/200 1544 GET <url>.gif - FIRST_UP_PARENT/127.0.0.1 text/html
> TCP_MISS/304 232 GET <url>.gif - DIRECT/216.239.59.103 text/html
Which is OK, except that the information was stale which is unrelated to
no_cache.
> Without no_cache deny BACK :
>
> TCP_REFRESH_HIT/200 1544 GET <url>.gif - FIRST_UP_PARENT/127.0.0.1 text/html
> TCP_REFRESH_HIT/304 232 GET <url>.gif - DIRECT/216.239.59.103 text/html
The only difference here is that the parent had the object cached. In
both it was stale.
Oh I understand it's only a header, this is why there is text/html, so
it's work fine :D.
And if there is a purge this is ok for my configuration. I will try to
run test to detect purge later.
Again:
> > If in doubt send access.log details with log_mime_hrds on from both
> > squids.
I have only one Squid, one cache and acl myport to distinct FRONT and
BACK. log_mime_headers is text/html or image/gif isn't it ?
Tanks you.
Aurélien
