Hello Hrvoje,
On Friday, November 7, 2003 at 11:50:53 PM +0100, Hrvoje Niksic wrote:
Wget uses the `Keep-Alive' request header to request persistent
connections, and understands both the HTTP/1.0 `Keep-Alive' and the
HTTP/1.1 `Connection: keep-alive' response header.
This doesn't seem
Alain Bench [EMAIL PROTECTED] writes:
Hello Hrvoje,
On Friday, November 7, 2003 at 11:50:53 PM +0100, Hrvoje Niksic wrote:
Wget uses the `Keep-Alive' request header to request persistent
connections, and understands both the HTTP/1.0 `Keep-Alive' and the
HTTP/1.1 `Connection: keep-alive'
On Tue, 11 Nov 2003, Hrvoje Niksic wrote:
I think the difference is that Wget closes the connection when it decides
not to read the request body. For example, it closes on redirections
because it (intentionally) ignores the body.
Another approach could be to read and just ignore the body of
From: Hrvoje Niksic [mailto:[EMAIL PROTECTED]
With the HEAD method you never know when you'll stumble upon a CGI
that doesn't understand it and that will send the body anyway. But
maybe it would actually be a better idea to read (and discard) the
body than to close the connection and reopen
Herold Heiko [EMAIL PROTECTED] writes:
From: Hrvoje Niksic [mailto:[EMAIL PROTECTED]
With the HEAD method you never know when you'll stumble upon a CGI
that doesn't understand it and that will send the body anyway. But
maybe it would actually be a better idea to read (and discard) the
body
I noticed this with the latest CVS Wget:
$ wget ftp://ftp.deepspace6.net/pub/ds6/sources/nc6/nc6-0.5.tar.bz2
--23:45:52-- ftp://ftp.deepspace6.net/pub/ds6/sources/nc6/nc6-0.5.tar.bz2
= `nc6-0.5.tar.bz2'
Resolving ftp.deepspace6.net... 2001:760:204:10:10:a7ff:fe16:27f4,
