On 22 Mar 2002 at 3:59, Hrvoje Niksic wrote: > Ian, why do you think this should not be allowed by default? A > command-line option is easy to miss, and honoring this looks like a > neat idea. Am I missing something?
Mainly that it is a change in behavior as Wget currently derives filenames from the URL. Honoring Content-Disposition is also incompatible with the current implementation of the --no-clobber option, but could be made compatible (see below). It's also not part of the HTTP standard (RFC 2616 s. 15.5). If Content-Disposition is honored by default, there should be an option to disable it (--no-honor-content-disposition ?). For --no-clobber, the current implementation does not do a HTTP transfer if the local file (name derived from URL) exists. If the option to honor Content-Disposition is turned on, then if the local file (name derived from URL)does not exist, --no-clobber should first download the HTTP header only. If there is a Content- Disposition header, then update the local filename and check whether the local file exists. If it doesn't then do a full retrieval otherwise leave the local file alone and indicate to the calling function that the transfer was successful. I'm not sure how deeply David wants to delve into the workings of the various Wget options such as --no-clobber, but he may wish to ignore that for now.
