Does HTTP allow this?

2003-11-08 Thread Hrvoje Niksic
Assume that Wget has retrieved a document from the host A, which hasn't closed the connection in accordance with Wget's keep-alive request. Then Wget needs to connect to host B, which is really the same as A because the provider uses DNS-based virtual hosts. Is it OK to reuse the connection to A

Retire little-used one-letter options

2003-11-08 Thread Hrvoje Niksic
It's a shame that we cannot assign a meaningful value to `-s' (such as "--silent") because it's already spent on the obscure `--save-headers'. It might be a good idea to retire some of the really obscure short options and leave those letters available for better things. This patch retires the opt

Wget 1.9.1-rc1 available for testing

2003-11-08 Thread Hrvoje Niksic
The 1.9.1 release will fix several problems noticed in the 1.9 release, and several bugs reported in the Debian bug tracking system. This is the first, and hopefully only, release candidate. Please test it as widely as possible. Get it from: ftp://gnjilux.srk.fer.hr/pub/unix/util/wget/.betas

Re: keep alive connections

2003-11-08 Thread Hrvoje Niksic
Daniel Stenberg <[EMAIL PROTECTED]> writes: > On Fri, 7 Nov 2003, Hrvoje Niksic wrote: > >> Persistent connections were available prior to HTTP/1.1, although they were >> not universally implemented. Wget uses the `Keep-Alive' request header to >> request persistent connections, and understands b

Re: keep alive connections

2003-11-08 Thread Daniel Stenberg
On Fri, 7 Nov 2003, Hrvoje Niksic wrote: > Persistent connections were available prior to HTTP/1.1, although they were > not universally implemented. 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 `C