Re: [Zope] RE: [Zope-dev] Fighting with ZServer
weboats@web-oats.com 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. That may be possible.
However, this avoids browser caching of the images (at least until 2002-3-15). I think, disabling the caching is not a good thing. Furthermore, it does not explain, why netscape displays the image as broken. It should get a nice 304 response which is usually handles correctly. By the way, Zope should cope with rounding problems for the "If-Modified-Since" headers. Dieter
Dieter Maurer wrote:
weboats@web-oats.com 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
participants (2)
-
Chris Withers -
Dieter Maurer