Bug in OW3 Beta9 (Broken URLs) "Underflow, Attempted read off end..."

[Robert C. Doss Jr.]

Ken Case (kc at omnigroup.com) wrote:
>One big difference between HTTP 1.0 and HTTP 1.1 is that HTTP 1.1 
>servers are allowed to drop the connection to the client at any time, 
>for any reason or no reason. The client is expected to be prepared 
>to reconnect and rerequest their file (hopefully with a byte range 
>which skips the data already retrieved) at all times.

For me, the case has been that HTTP connections are terminated at
almost every site (including www.omnigroup.com) and OmniWeb 3.0b9
tries to rerequest the data from the beginning. This happens quite
often with in line images to the effect that the slider which
displays how much of an image has been downloaded progresses about
half way, stops and then starts over from the beginning again ad
infinitum. I was forced to turn off images just so I can see the
web pages.  Another "fun" problem I've been having is when OmniWeb
3,0b9 loads only part of the page, begins to render it, loses the
connection, refetches what it already has, and recursively renders
the page appending to what it already has. I sit there and watch
my window slowly fill up with the first couple of lines repeated
over and over again until I hit stop. I had to switch to using
either OmniWeb 3.0b8 or OmniWeb 2.7 just to have a usable browser.


---
Robert C. Doss, Jr.
Voice: (916) 394-5653
Fax: (916) 394-5502
<rob at doss.org> MIME & NeXTMAIL O.K