[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lynx-dev partial display (was: on caching)

From: Leonid Pauzner
Subject: Re: lynx-dev partial display (was: on caching)
Date: Wed, 18 Nov 1998 21:46:43 +0300 (MSK)

> But if a client sends a request line with "HTTP/1.1", then the servers
> is entitled to assume that the client
>  - wants persistent connections (unless "Connection: close" is sent)

One problem in partial display mode remind me this.
while accesing certain rare sites with lynx
I got repainting the screen on _previous_ document, not the downloading one,
so I analize the trace and add a semaphore against HText_new().

The only side information on that problemical sites -
they are not Apache and are not sending "Connection: close"
(and lynx send HTTP/1.0 as usual).

>  - understands "Transfer-Encoding: chunked"
>  - understands intermediate responses like "100 Continue" (probably;
>    not sure whether something has changed there)
> So there are no good reasons to pretend we are fully implementing HTTP 1.1,
> and there are good reasons not to do so.  (Except in your own private
> copy of lynx, to see what would go wrong...)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]