W3C home > Mailing lists > Public > www-jigsaw@w3.org > March to April 1999

AW: AW: Problem in accessing GIF files

From: Werner Hennrich <weHe@TeleWeb.at>
Date: Wed, 3 Mar 1999 09:02:45 -0500 (EST)
To: "Www-Jigsaw" <www-jigsaw@w3.org>
Message-ID: <000101be657e$7fe48540$879f22c3@stuwehe.telekabel.at>
Hello Yves,

thanks for your explanation - sounds very reasonable.

But the question remains: why does MSIE4 not have the same problem with
other Http/1.1 compliant servers?

AND: even if JigSaw is 'right' about its implementation of Http/1.1, if that
server cannot be used for _that_ client, which uses remain for JigSaw, even
if it is made by the W3C.

thanks & regards,
Werner


> -----Ursprüngliche Nachricht-----
> Von: Yves Lafon [mailto:ylafon@w3.org]
> Gesendet am: Dienstag, 2. März 1999 16:22
> An: Werner Hennrich
> Cc: Www-Jigsaw
> Betreff: Re: AW: Problem in accessing GIF files
>
> On Tue, 2 Mar 1999, Werner Hennrich wrote:
>
> > I'm having the same problem with JigSaw.
> > But it turned out that this is bound to using MSIE.
> > When I use Netscape, JigSaw works as expected.
>
> Jigsaw is HTTP/1.1. This means that connections are kept open. and some
> browsers seems to have problem with this (got 100% of... and waiting).
> On the Jigsaw side, the buffer is flushed and all the bytes are sent, as
> tcpdump shown.
>
>       /\          - Yves Lafon - World Wide Web Consortium -
>   /\ /  \        Architecture Domain - Jigsaw Activity Leader
>  /  \    \/\
> /    \   /  \   http://www.w3.org/People/Lafon - ylafon@w3.org
>
>
Received on Wednesday, 3 March 1999 09:03:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 9 April 2012 12:13:29 GMT