🚀 go-pugleaf

ian@isis.demon.co.uk (Ian Smith) wrote:
>
>Anybody know what the options are for how webpage servers terminate 
>their page transmissions ?

There is either keep-alive (aka persistent connections) or no
keep-alive. HTTP/1.0 doesn't include the keep-alive features, so if
you are using that protocol the connection should close immediately
after the response has been sent.

>My attention has been drawn to www.juge.com which does something unique 
>(in my experience) when it sends it's index page. In YAN (and I'd expect 
>anything else using an httpcli based on John Washington's original) the 
>page comes through OK, but the http client still waits for more, 
>apparently not realizing that the file transmission is complete. Running 
>through a proxy server, however, it's perfectly normal, which suggests 
>that the server is sending something which rings a proxy server's bell, 
>but not the httpcli's. The question is, what ?

I have seen interoperability bugs like this before -- particularly,
Netscape Enterprise Server tries to do keep-alive with HTTP/0.9
requests. This is a bit of a disaster since HTTP/0.9 has no way to
know the data is complete other than by observing that the connection
has closed, wheras HTTP/1.* has Content-Length: headers.

To give any definitive answer, I'd have to see a dump of the complete
exchange, particularly the HTTP/x.x version tags on the requests and
responses, and the contents of any Connection: headers. Note that our
current proxy caches do not all support persistent connections.

Tony.
-- 
                 yyyyhngbgyhntthy xgdf**f.a.n.finch
                                               fanf@demon.net
                                                       dot@dotat.at