[Zope] 2.1.6 will be your problem...

Chris Withers chrisw@nipltd.com
Mon, 04 Sep 2000 12:32:54 +0100

"T.J. Mannos" wrote:
> Yes, I have, and I spent hours tearing apart my site thinking I'd seriously
> screwed-up when suddenly all my images refused to load.  But that was just
> on my Solaris 2.6 server.  PCs and even Macs render my pages beautifully.
> It's just Netscape Communicator for Solaris that causes a problem.  I don't
> have a clue.

Yup, this is 'the Netscape with Images problem' :-(

> 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.

This does seem a lot like the "If-Modified-Since problem" in 2.1.6
caused by certain versions of Netscape sending crap header information
back to Zope, and zope throwing an exception.

IIRC, 2.2 handles this much better...

Check these bugs and see if any help:

And try it with 2.2 to see if it's still broken...