----- Original Message -----
From: "Daniel Stenberg" <daniel_at_haxx.se>
To: "Jacky Lam" <sylam_at_emsoftltd.com>
Cc: "libcurl Mailing list" <curl-library_at_lists.sourceforge.net>
Sent: Friday, April 05, 2002 10:52 PM
Subject: Re: header only response [PATCH]

> On Fri, 5 Apr 2002, Jacky Lam wrote:
>
> > > > "HTTP 304 Not Modified\r\n\r\n".
> > > > Just one line finished response. Do you have any idea?
> > >
> > > Is that a 1.0 or 1.1 reply when you see this? What happens with the
> > > connection, is it still alive?
>
> > The reply is 1.0 and I have explicitly included "keep-alive" in the
> > request header.
>
> I'm sorry, but I can't see how I can repeat/produce this problem to see
what
> happens.

    Here is the url producing this problem: http://www.netvigator.com When
you take a look of the HTTP packet sent by the server after pressing
reloading the page in Mozilla. You can see that kind of response.

>
> If the connection actually is kept alive, then I'd say that this is a
problem
> in the server end. libcurl can't possible know when the response ends if
kept
> alive with no content-length, no close and no chunked transfer is used...
>

    Yes. I think so. However, I think it is good of software to have certain
kind of fault tolerence (at least a browser should do, just like IE and
Netscape). I will look into this problem and try to provide a good quality
patch for you.

    Thx.

Jacky
Received on 2002-04-06