> On Tue, Jan 20, 2009 at 5:31 PM, Matus UHLAR - fantomas <uhlar_at_fantomas.sk>
> > Haven't you mistaken 304 for 200 ? the 200 means that the server is sending
> > the whole content to the client, while 304 means server is telling the
> > client that the content on client is still fresh. So with big expire time
> > you could expect much of 304's and little of 200's.
On 20.01.09 23:55, howard chen wrote:
> My understanding...
>
> 304 is used if a user conditioinally request for an object, e.g. by
> pressing F5.
user can't conditionally request an object. It's the client (browser, proxy)
that should do that if it has non-expired version. Unless is is set up to
always fetch the conent.
refresh afaik means request to unconditional reloading of an object.
> If expire is set and still fresh, client NO need to contact my server,
> so my log cannot see 304 at all...
Ahm, true. But after object is expired, the browser/cache still may have it
in the cache and try to revalidate it...
> so seeing too many 304 is abnormal...and you see my example above is
> serious in IE only.
the ie_refresh setting mentioned by Amos probably
-- Matus UHLAR - fantomas, uhlar@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. WinError #98652: Operation completed successfully.Received on Wed Jan 21 2009 - 10:24:35 MST
This archive was generated by hypermail 2.2.0 : Wed Jan 21 2009 - 12:00:19 MST