-----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 with prior versions and any "old" script would need to be > rewritten. > b) It's impossible to pre-guess the filename and thus it is not so well > suited for script-usage. > > I would like to have this feature enabled by some "--interactive" switch > (which could include more options and might be easier to find) or as you > suggested as default with an disable switch.
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 up using Content-Disposition somewhere. Note that it is not available at all in any release version of Wget; only in the current development versions. We will be releasing Wget 1.11 very shortly, which will include the --content-disposition functionality; however, this functionality is EXPERIMENTAL only. It doesn't quite behave properly, and needs some severe adjustments before it is appropriate to leave as default. As to breaking old scripts, I'm not really concerned about that (and people who read the NEWS file, as anyone relying on previous behaviors for Wget should do, would just need to set --no-content-disposition, when the time comes that we enable it by default). - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHVDmo7M8hyUobTrERAtYoAKCR6bYexmpqj5Wud6p9evttgDCMgwCfdoQY oXbPU6EwfQhQhfN0Pi9wC+E= =t6et -----END PGP SIGNATURE-----
