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 to work together with --timestamping: Each HEAD
and each possible GET uses a new connection. The server keeps
responding:
| HTTP/1.0 200 OK
| [...]
| Connection: Keep-Alive
| Keep-Alive: timeout=15, max=5
But Wget 1.9 does each time:
| Created socket 3.
| [snip request/response]
| Registered fd 3 for persistent reuse.
| Closing fd 3
| Invalidating fd 3 from further reuse.
| Remote file is newer, retrieving.
| Created socket 3.
| [and so on]
Tcpdump confirms the TCP session is FIN closed by Wget.
Without --timestamping Wget keeps "Reusing fd 3." and closing it
only once every 6 files (first + 5 more). At this moment the FIN would
in any case be initiated by the server if not by Wget. Test made on an
old Apache 1.1.3, but it seems the same with other servers.
BTW, it's nice to see you back and active, Hrvoje! :-)
Bye! Alain.
--
Mutt 1.5.5.1 is released.
