Micah Cowan [EMAIL PROTECTED] writes:
Actually, the reason it is not enabled by default is that (1) it is
broken in some respects that need addressing, and (2) as it is currently
implemented, it involves a significant amount of extra traffic,
regardless of whether the remote end actually ends
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hrvoje Niksic wrote:
Micah Cowan [EMAIL PROTECTED] writes:
Actually, the reason it is not enabled by default is that (1) it is
broken in some respects that need addressing, and (2) as it is currently
implemented, it involves a significant amount
Micah Cowan [EMAIL PROTECTED] writes:
I thought the code was refactored to determine the file name after
the headers arrive. It certainly looks that way by the output it
prints:
{mulj}[~]$ wget www.cnn.com
[...]
HTTP request sent, awaiting response... 200 OK
Length: unspecified
Hi!
I have noticed that wget doesn't automatically use the option
'--content-disposition'. So what happens is when you download something
from a site that uses content disposition, the resulting file on the
filesystem is not what it should be.
For example, when downloading an Ubuntu torrent
Hi,
we know this. This was just recently discussed on the mailinglist and I
agree with you.
But there are two arguments why this is not default:
a) It's a quite new feature for wget and therefore would brake
compatibility with prior versions and any old script would need to be
rewritten.
b) It's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matthias Vill wrote:
Hi,
we know this. This was just recently discussed on the mailinglist and I
agree with you.
But there are two arguments why this is not default:
a) It's a quite new feature for wget and therefore would brake
compatibility
