[Zope] Unexpected script behavior

Passin, Tom tpassin@mitretek.org
Wed, 4 Dec 2002 14:43:12 -0500


[ Michael Long]

I forget the details, but it involves the "expires" date/time HTTP
header AFAIR.  You should be able to search the Zope list (and the Zope
site).  I know it has been discussed here before.

Cheers,

Tom P

>=20
> Thanks for the info. It appears that it is the browser that=20
> is caching the data. What is the header control that can be=20
> used to prevent this.
>=20
> Thanks,
> Mike
>=20
> > [ Michael Long]
> > >=20
> > > I am getting unexpected results from my python script. Here
> > > is a snippet form the python script:
> > >...
> >=20
> > > After the person is successfully deleted from the database
> > > another call to the database is made to get a list of people=20
> > > and set that to 'PersonList'. This variable is then used to=20
> > > render the page. The problem is that the deleted person still=20
> > > shows up in the rendered page. When the page is called a=20
> > > second time the correct data is shown. I have validated that=20
> > > the data is deleted from the database when expected. Why=20
> > > would the 'PersonList' not have the correct data?
> > >=20
> >=20
> > Sounds like that browser is displaying a cached verison of=20
> the page. =20
> > If it is the browser doing the caching, you can set a header to=20
> > control it. If it is Zope, you can change the cache setup.
> >=20
> > Cheers,
> >=20
> > Tom P
> >=20
> >=20
>=20
>=20
>=20
> _______________________________________________
> Zope maillist  -  Zope@zope.org=20
> http://lists.zope.org/mailman/listinfo/zope
> **   No cross=20
> posts or HTML encoding!  **
> (Related lists -=20
>  http://lists.zope.org/mailman/listinfo/zope-announce
>  http://lists.zope.org/mailman/listinfo/zope-dev )
>=20