|
From: | Jonas H. |
Subject: | [Bug-wget] Connection: Keep-Alive behaviour |
Date: | Thu, 30 Dec 2010 14:29:14 +0100 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101211 Lanikai/3.1.7 |
Howdy!In the process of testing my HTTP server implementation I stumbled upon a Wget weird behaviour regarding keep-alive connections.
Wget requests a `Connection: Keep-Alive`, my server responds in chunks (`Transfer-Encoding: chunked`). Wget receives the empty sentinel chunk but does not close the connection although it hasn't got any more requests sticking around in its pipeline. The reason for this behaviour is, I guess, that my server does /not/ send a `Connection: Keep-Alive` header in the response.
I think Wget should close the connection even though the `Connection: Keep-Alive` header is missing from the response. Why should it wait for more data? It's obvious that the server has no data left to send after the sentinel chunk, isn't it?
Jonas
[Prev in Thread] | Current Thread | [Next in Thread] |