W3C home > Mailing lists > Public > www-jigsaw@w3.org > July to August 1996

Strange Jigsaw Behaviour under Win95 - Solution -

From: Nexus <nexus@adv.es>
Date: Wed, 10 Jul 1996 19:42:22 +0200
Message-ID: <31E3EB7D.38B@adv.es>
To: Anselm Baird-Smith <abaird@w3.org>
CC: www-jigsaw@w3.org
Here's *at least* a Subject change:

So What was the problem with W95 ???

As Anselm pointed out:

> There is a bug in netscape 2.0 and keep alive connections. When Jigsaw
> emits an error, Netscape (<= 2.x hangs badly). If you're using 2.0 you
> might consider upgrading to 3.0 (which is better anyway), or turn the
> Jigsw keep-alive flag to false.

Well, this bug seems to be present in Netscape Atlas Prerelease 2, and
the Internet Explorer 2.0; wich claims to be Navigator 1.22 compatible
(it inherited the same bug. Really Impressive!).

Turning off the keep-alive flag fixed this problem. (If I knew before...)

And that's what I think it happened: (pretty impressive)

Jigsaw Emmited an error --> The browser thinks there's some *critical* thing on
the server and tries to close his output stream (I suppose that's where GET, and 
POST commands go).

Open question:
So why looks like the browser is *still* searching or receiving data ???
Msie 2.0 Reports something like it's Getting the URL. What does it mean ??
Is Jigsaw sending data and the browser doesn't know it: remenber error meant
that the brouser had his output stream closed.

Thank you folks for spending your time reading those boring postings
about esoteric bugs.

I~nigo Gonzalez Ponce  nexus@adv.es ; nexus@freenet.hut.fi
Snail: Juan Diges Anton 27 6C 19003 Guadalajara (Spain)
Home : +34 49 224 656 <remember GMT+01> .._O-)
Received on Wednesday, 10 July 1996 13:38:19 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:25:29 UTC