Re: [Zope] If-Modified-Since problem again?!
Chris Withers writes: > Dieter Maurer wrote: > > By the way, Zope should cope with rounding problems > > for the "If-Modified-Since" headers. > > AFAIK, Brian Lloyd fixed this with a pretty generalised try...except in > Image.py > If stuff is still getting through, we should narrow it down further... No traceback, because no exception. I speak of a true rounding problem: the image is modified at "x" (expressed in seconds) Zope sends "x" converted to a date/time string as "Last-Modified" Zope receives the date/time string back as "If-Modified-Since". Zope converts it to a "long", say y. *BUT* y is not x, it is "x-1". Of cause, this does not happen for all modification times. But there are not too few of them. Dieter ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
[Zope] If-Modified-Since problem again?!
Dieter Maurer wrote: > > [EMAIL PROTECTED] writes: > > To your image in properites add a string property called > > > > Last-Modified > > > > with value > > > > Wed, 15 Mar 2002 19:02:17 GMT > > > > And your broken image problem will disappear. What version of Zope is this with? > However, this avoids browser caching of the images (at > least until 2002-3-15). I think, disabling the caching > is not a good thing. Definitely! > By the way, Zope should cope with rounding problems > for the "If-Modified-Since" headers. AFAIK, Brian Lloyd fixed this with a pretty generalised try...except in Image.py If stuff is still getting through, we should narrow it down further... A traceback for this would go a long way cheers, Chris ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
