RE: [Zope-dev] Fighting with ZServer
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. This is not zope specific, I think it's apache since I've had the problem with PHP4 using a fusebox architecture. -Kevin Smith
Since this afternoon, I am fighting with ZServer. Currently, it seems Zserver is winning .... I do not understand, what I see...
At work: Zope 2.1.6, Sparc Solaris 2.7, Linux Netscape 4.51
Sometimes, images are not shown by Netscape (broken image). No "simple" reload is able to change this, however a "forced" reload lets Netscape show the image correctly. From then on, the image is always shown correctly: by "simple" reload, "forced" reload or directly (served from cache).
The strange thing, inside "Image.index_html" the failing "simple" reload and the succeeding "forced" reload look completely identical.
At home: Zope 2.1.6, Intel Linux 2, Linux Netscape 4.5
All images are always shown correctly. However, there is no log entry in "var/Z2.log" for about 50 % of the requests that are answered by a 304 response. It is non-deterministic whether a log entry is written or not.
Did you ever see something like this?
Dieter
participants (1)
-
weboats@web-oats.com