Re: [Zope-dev] Errors causing half rendered pages
Chris Withers writes:
I'm still debugging and writing the navtree code I've mentioned before and I've noticed that not infrequently, when rendering a page that causes and error, I get a half rendered page rather than a nice Zope error page.
This is a bit waffly to put into the collector so I was wondering if anyone else has had similar experiences? I saw this only when buggy HTML was generated. When I viewed the HTML source my Netscape browser sometimes showed me blinking parts that located the errors.
Dieter
Dieter Maurer wrote:
I saw this only when buggy HTML was generated. When I viewed the HTML source my Netscape browser sometimes showed me blinking parts that located the errors.
Nope, this was with IE... I viewed source and sure enough, it ended after a few lines. I guess it might have something to dop with streaming HTTP output, but I don't think Zope uses that... Ideas anyone? Chris
On Sun, Jul 16, 2000 at 10:38:41PM +0100, Chris Withers wrote:
Dieter Maurer wrote:
I saw this only when buggy HTML was generated. When I viewed the HTML source my Netscape browser sometimes showed me blinking parts that located the errors.
Nope, this was with IE...
I viewed source and sure enough, it ended after a few lines.
I guess it might have something to dop with streaming HTTP output, but I don't think Zope uses that...
Ideas anyone?
THis rings vague bells of IIS or some other proxy server or somthing converting LF tp CRLF but not updating the Content-Length header, thus having your browser drop part of the transmission. I could be talking absolute nonsense of course. -- Martijn Pieters | Software Engineer mailto:mj@digicool.com | Digital Creations http://www.digicool.com/ | Creators of Zope http://www.zope.org/ | ZopeStudio: http://www.zope.org/Products/ZopeStudio -----------------------------------------------------
Martijn Pieters wrote:
THis rings vague bells of IIS or some other proxy server or somthing converting LF tp CRLF but not updating the Content-Length header, thus having your browser drop part of the transmission.
I could be talking absolute nonsense of course.
To much work on ZopeStudio I think ;-) It was way more than a few characters off, usually I would get about 20% of the page... To be fair, it's only ever happened when I'm causing an error, but it's not healthy... Like those invalid header (0) errors that still pop up if you don't have <HTML><HEAD></HEAD></HTML> on the frotn of anything that gets squirted over HTTP (whether it's HTML or not ;-) I'm betting this is the fault of that BASE tag too ;-) good luck with ZS, Chris
participants (3)
-
Chris Withers -
Dieter Maurer -
Martijn Pieters