Hi Jonas, wget 1.12 doesn't support HTTP/1.1 so the "Transfer-Encoding: chunked" header is not considered. The development version[1] supports HTTP/1.1. If you are already using it, can you please attach the "wget -d" output?
In any case, wget specifies HTTP/1.0 in the request, your web server shouldn't use features not present in this version of the protocol. Cheers, Giuseppe 1) https://savannah.gnu.org/bzr/?group=wget "Jonas H." <[email protected]> writes: > 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
