[Zope-dev] Last-modified and bobobase_modification_time

[Adrian Hungate]

Ah, well, that is not quite true. Zope (And apache, IIS, and others) may do
the "right thing" and set or not set the headers, but IE at least definately
DOES NOT do the correct thing when it comes to caching on the client (Even
with caching disabled it still caches when it feels like it).

Until clients improve, caching is just bad IMHO.

Adrian...

--
Adrian Hungate
EMail: adrian@haqa.co.uk
Web: http://www.haqa.co.uk

----- Original Message -----
From: "Wei He" <hewei@mail.ied.ac.cn>
To: "Toby Dickenson" <tdickenson@geminidataloggers.com>
Cc: "Dieter Maurer" <dieter@handshake.de>; "R. David Murray"
<bitz@bitdance.com>; "Chris Withers" <chrisw@nipltd.com>; "Casey Duncan"
<casey@zope.com>; <zope-dev@zope.org>
Sent: Thursday, June 20, 2002 2:45 PM
Subject: Re: [Zope-dev] Last-modified and bobobase_modification_time


> On Thu, 20 Jun 2002, Toby Dickenson wrote:
>
> > > In either case, Zope's current implementation needs to be
> > > changed. Because it will give the client a false impression that a
page has
> > > not changed but actually it did.
> >
> > What part of Zope gets this wrong?
> >
>
> I just realized that the Last-Modified header in a GET request is NOT
> sent for a dynamic page. I was always asuming that it is the same as the
> HEAD request of the same URL.
>
> So at least the user can get correct information cause the client cache
> function will not work. Whether a cache server can handle this
> situation or whether RFC allows doing this (haven't read yet) is not
> a big problem.
>
> Sorry to everyone. And thank all of you.
>
> Wei He
>
>
>
>
>
> _______________________________________________
> Zope-Dev maillist  -  Zope-Dev@zope.org
> http://lists.zope.org/mailman/listinfo/zope-dev
> **  No cross posts or HTML encoding!  **
> (Related lists -
>  http://lists.zope.org/mailman/listinfo/zope-announce
>  http://lists.zope.org/mailman/listinfo/zope )
>