[10167] in www-talk@info.cern.ch
Re: Navigator & the closed socket (was: POST forms & Netscape
daemon@ATHENA.MIT.EDU (Inigo Lopez)
Fri Jul 26 03:48:31 1996
To: www-talk@w3.org
In-Reply-To: <199607251717.KAA04135@pele.ckm.ucsf.edu>
Date: Fri, 26 Jul 1996 09:38:19 +0200
From: Inigo Lopez <ilopez@fundesco.es>
Resent-From: www-talk@w3.org
En fecha/On Thu, 25 Jul 1996 10:17:59 -0700 marc@ckm.ucsf.edu expuso/wro=
te:
> |>Netscape does NOT close the connection but opens a new connection to =
the =
> |>server for each inline image it needs. After it has received all the =
images, =
> |>it closes all the > connections. This happens even if the server resp=
onds =
> |>with HTTP/1.1 and Connection: keep-alive.
> =
> All implementations of HTTP/1.1 are technically speculative at this poi=
nt
> since the draft hasn't been finalized. In any case, unless a client
> issues an HTTP request at level 1.1 or higher (does navigator actually =
do =
> this?) a server cannot respond with an HTTP/1.1 response.
Navigator still issues an HTTP/1.0 request. I just wrote a null HTTP serv=
er =
that
would accept HTTP connections and keep them alive, to see what the client=
does.
I even tried to respond with an HTTP/1.1 (I know I shouldn't) just to see=
what
happened.
The question here is: Why is Netscape sending "Connection: Keep-Alive" ??=
?
+--------------------------------------------------------------+
| O I=F1igo L=F3pez C=EDa ilopez@fundesco.es |
| o O Fundesco - Dpto. Redes |
| . o O Plaza de la Independencia, 6 Tel: +34-1-3300735 |
| . o 28001 Madrid Fax: +34-1-3300675 |
| . Spain |
+--------------------------------------------------------------+
