X-Git-Url: http://sjero.net/git/?a=blobdiff_plain;f=doc%2Fwget.texi;h=fed188ad982e1690234c10d3e20d41f69cc72dc1;hb=0e6f1c2dacb7027247518eb52ab53c92c6d8c467;hp=950c1eaac8a0266b9f379cc8fe5aa7ba61326520;hpb=b5c9573ad6396acf3e4e33d0ae0db65b413b0d66;p=wget diff --git a/doc/wget.texi b/doc/wget.texi index 950c1eaa..fed188ad 100644 --- a/doc/wget.texi +++ b/doc/wget.texi @@ -20,9 +20,9 @@ @set Wget Wget @c man title Wget The non-interactive network downloader. -@dircategory Network Applications +@dircategory Network applications @direntry -* Wget: (wget). The non-interactive network downloader. +* Wget: (wget). Non-interactive network downloader. @end direntry @copying @@ -31,7 +31,8 @@ data. @c man begin COPYRIGHT Copyright @copyright{} 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, -2004, 2005, 2006, 2007, 2008, 2009, 2010 Free Software Foundation, Inc. +2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011 Free Software Foundation, +Inc. @iftex Permission is granted to make and distribute verbatim copies of @@ -63,7 +64,6 @@ Documentation License''. @ignore @c man begin AUTHOR Originally written by Hrvoje Niksic . -Currently maintained by Micah Cowan . @c man end @c man begin SEEALSO This is @strong{not} the complete manual for GNU Wget. @@ -190,7 +190,9 @@ gauge can be customized to your preferences. Most of the features are fully configurable, either through command line options, or via the initialization file @file{.wgetrc} (@pxref{Startup File}). Wget allows you to define @dfn{global} startup files -(@file{/usr/local/etc/wgetrc} by default) for site settings. +(@file{/usr/local/etc/wgetrc} by default) for site settings. You can also +specify the location of a startup file with the --config option. + @ignore @c man begin FILES @@ -477,6 +479,9 @@ Turn off verbose without being completely quiet (use @samp{-q} for that), which means that error messages and basic information still get printed. +@item --report-speed=@var{type} +Output bandwidth as @var{type}. The only accepted value is @samp{bits}. + @cindex input-file @item -i @var{file} @itemx --input-file=@var{file} @@ -524,6 +529,10 @@ presence of a @code{BASE} tag in the @sc{html} input file, with For instance, if you specify @samp{http://foo/bar/a.html} for @var{URL}, and Wget reads @samp{../baz/b.html} from the input file, it would be resolved to @samp{http://foo/baz/b.html}. + +@cindex specify config +@item --config=@var{FILE} +Specify the location of a startup file you wish to use. @end table @node Download Options, Directory Options, Logging and Input File Options, Invoking @@ -706,9 +715,12 @@ different meaning to one dot. With the @code{default} style each dot represents 1K, there are ten dots in a cluster and 50 dots in a line. The @code{binary} style has a more ``computer''-like orientation---8K dots, 16-dots clusters and 48 dots per line (which makes for 384K -lines). The @code{mega} style is suitable for downloading very large +lines). The @code{mega} style is suitable for downloading large files---each dot represents 64K retrieved, there are eight dots in a cluster, and 48 dots on each line (so each line contains 3M). +If @code{mega} is not enough then you can use the @code{giga} +style---each dot represents 1M retrieved, there are eight dots in a +cluster, and 32 dots on each line (so each line contains 32M). Note that you can set the default style using the @code{progress} command in @file{.wgetrc}. That setting may be overridden from the @@ -841,9 +853,7 @@ If you don't want Wget to wait between @emph{every} retrieval, but only between retries of failed downloads, you can use this option. Wget will use @dfn{linear backoff}, waiting 1 second after the first failure on a given file, then waiting 2 seconds after the second failure on that -file, up to the maximum number of @var{seconds} you specify. Therefore, -a value of 10 will actually make Wget wait up to (1 + 2 + ... + 10) = 55 -seconds per file. +file, up to the maximum number of @var{seconds} you specify. By default, Wget will assume a value of 10 seconds. @@ -868,7 +878,7 @@ recommendation to block many unrelated users from a web site due to the actions of one. @cindex proxy -@itemx --no-proxy +@item --no-proxy Don't use proxies, even if the appropriate @code{*_proxy} environment variable is defined. @@ -969,7 +979,7 @@ are outside the range of @sc{ascii} characters (that is, greater than whose encoding does not match the one used locally. @cindex IPv6 -@itemx -4 +@item -4 @itemx --inet4-only @itemx -6 @itemx --inet6-only @@ -1184,10 +1194,7 @@ Note that filenames changed in this way will be re-downloaded every time you re-mirror a site, because Wget can't tell that the local @file{@var{X}.html} file corresponds to remote URL @samp{@var{X}} (since it doesn't yet know that the URL produces output of type -@samp{text/html} or @samp{application/xhtml+xml}. To prevent this -re-downloading, you must use @samp{-k} and @samp{-K} so that the original -version of the file will be saved as @file{@var{X}.orig} (@pxref{Recursive -Retrieval Options}). +@samp{text/html} or @samp{application/xhtml+xml}. As of version 1.12, Wget will also ensure that any downloaded files of type @samp{text/css} end in the suffix @samp{.css}, and the option was @@ -1444,7 +1451,7 @@ data, whereas @samp{--post-file} sends the contents of @var{file}. Other than that, they work in exactly the same way. In particular, they @emph{both} expect content of the form @code{key1=value1&key2=value2}, with percent-encoding for special characters; the only difference is -that one expects its content as a command-line paramter and the other +that one expects its content as a command-line parameter and the other accepts its content from a file. In particular, @samp{--post-file} is @emph{not} for transmitting files as form attachments: those must appear as @code{key=value} data (with appropriate percent-coding) just @@ -1453,6 +1460,11 @@ like everything else. Wget does not currently support @code{application/x-www-form-urlencoded}. Only one of @samp{--post-data} and @samp{--post-file} should be specified. +Please note that wget does not require the content to be of the form +@code{key1=value1&key2=value2}, and neither does it test for it. Wget will +simply transmit whatever data is provided to it. Most servers however expect +the POST data to be in the above format when processing HTML Forms. + Please be aware that Wget needs to know the size of the POST data in advance. Therefore the argument to @code{--post-file} must be a regular file; specifying a FIFO or something like @file{/dev/stdin} won't work. @@ -1493,6 +1505,34 @@ them (and neither will browsers) and the @file{cookies.txt} file will be empty. In that case use @samp{--keep-session-cookies} along with @samp{--save-cookies} to force saving of session cookies. +@cindex Other HTTP Methods +@item --method=@var{HTTP-Method} +For the purpose of RESTful scripting, Wget allows sending of other HTTP Methods +without the need to explicitly set them using @samp{--header=Header-Line}. +Wget will use whatever string is passed to it after @samp{--method} as the HTTP +Method to the server. + +@item --body-data=@var{Data-String} +@itemx --body-file=@var{Data-File} +Must be set when additional data needs to be sent to the server along with the +Method specified using @samp{--method}. @samp{--post-data} sends @var{string} as +data, whereas @samp{--post-file} sends the contents of @var{file}. Other than that, +they work in exactly the same way. + +Currently, @samp{--body-file} is @emph{not} for transmitting files as a whole. +Wget does not currently support @code{multipart/form-data} for transmitting data; +only @code{application/x-www-form-urlencoded}. In the future, this may be changed +so that wget sends the @samp{--body-file} as a complete file instead of sending its +contents to the server. Please be aware that Wget needs to know the contents of +BODY Data in advance, and hence the argument to @samp{--body-file} should be a +regular file. See @samp{--post-file} for a more detailed explanation. +Only one of @samp{--body-data} and @samp{--body-file} should be specified. + +Wget handles these requests in the same way that it handles @samp{--post-data} +and @samp{--post-file}. If you invoke Wget with @samp{--method=POST} and the server +responds with a redirect request, then Wget will revert to a GET request during the +redirection as is explained in @samp{--post-data}. + @cindex Content-Disposition @item --content-disposition @@ -1505,6 +1545,12 @@ This option is useful for some file-downloading CGI programs that use @code{Content-Disposition} headers to describe what the name of a downloaded file should be. +@cindex Content On Error +@item --content-on-error + +If this is set to on, wget will not skip the content when the server responds +with a http status code that indicates error. + @cindex Trust server names @item --trust-server-names @@ -1651,6 +1697,36 @@ not used), EGD is never contacted. EGD is not needed on modern Unix systems that support @file{/dev/random}. @end table +@cindex WARC +@table @samp +@item --warc-file=@var{file} +Use @var{file} as the destination WARC file. + +@item --warc-header=@var{string} +Use @var{string} into as the warcinfo record. + +@item --warc-max-size=@var{size} +Set the maximum size of the WARC files to @var{size}. + +@item --warc-cdx +Write CDX index files. + +@item --warc-dedup=@var{file} +Do not store records listed in this CDX file. + +@item --no-warc-compression +Do not compress WARC files with GZIP. + +@item --no-warc-digests +Do not calculate SHA1 digests. + +@item --no-warc-keep-log +Do not store the log file in a WARC record. + +@item --warc-tempdir=@var{dir} +Specify the location for temporary files created by the WARC writer. +@end table + @node FTP Options, Recursive Retrieval Options, HTTPS (SSL/TLS) Options, Invoking @section FTP Options @@ -1763,12 +1839,12 @@ case. @item -r @itemx --recursive Turn on recursive retrieving. @xref{Recursive Download}, for more -details. +details. The default maximum depth is 5. @item -l @var{depth} @itemx --level=@var{depth} Specify recursion maximum depth level @var{depth} (@pxref{Recursive -Download}). The default maximum depth is 5. +Download}). @cindex proxy filling @cindex delete after retrieval @@ -2277,6 +2353,8 @@ in @file{.wgetrc}. @item -A @var{acclist} @itemx --accept @var{acclist} @itemx accept = @var{acclist} +@itemx --accept-regex @var{urlregex} +@itemx accept-regex = @var{urlregex} The argument to @samp{--accept} option is a list of file suffixes or patterns that Wget will download during recursive retrieval. A suffix is the ending part of a file, and consists of ``normal'' letters, @@ -2293,6 +2371,9 @@ a description of how pattern matching works. Of course, any number of suffixes and patterns can be combined into a comma-separated list, and given as an argument to @samp{-A}. +The argument to @samp{--accept-regex} option is a regular expression which +is matched against the complete URL. + @cindex reject wildcards @cindex reject suffixes @cindex wildcards, reject @@ -2300,6 +2381,8 @@ comma-separated list, and given as an argument to @samp{-A}. @item -R @var{rejlist} @itemx --reject @var{rejlist} @itemx reject = @var{rejlist} +@itemx --reject-regex @var{urlregex} +@itemx reject-regex = @var{urlregex} The @samp{--reject} option works the same way as @samp{--accept}, only its logic is the reverse; Wget will download all files @emph{except} the ones matching the suffixes (or patterns) in the list. @@ -2311,6 +2394,9 @@ Analogously, to download all files except the ones beginning with expansion by the shell. @end table +The argument to @samp{--accept-regex} option is a regular expression which +is matched against the complete URL. + @noindent The @samp{-A} and @samp{-R} options may be combined to achieve even better fine-tuning of which files to retrieve. E.g. @samp{wget -A @@ -3043,7 +3129,7 @@ display properly---the same as @samp{-p}. Change setting of passive @sc{ftp}, equivalent to the @samp{--passive-ftp} option. -@itemx password = @var{string} +@item password = @var{string} Specify password @var{string} for both @sc{ftp} and @sc{http} file retrieval. This command can be overridden using the @samp{ftp_password} and @samp{http_password} command for @sc{ftp} and @sc{http} respectively. @@ -3170,6 +3256,10 @@ as @samp{--secure-protocol=@var{string}}. Choose whether or not to print the @sc{http} and @sc{ftp} server responses---the same as @samp{-S}. +@item show_all_dns_entries = on/off +When a DNS name is resolved, show all the IP addresses, not just the first +three. + @item span_hosts = on/off Same as @samp{-H}. @@ -3521,34 +3611,36 @@ internal networks from the rest of Internet. In order to obtain information from the Web, their users connect and retrieve remote data using an authorized proxy. +@c man begin ENVIRONMENT Wget supports proxies for both @sc{http} and @sc{ftp} retrievals. The standard way to specify proxy location, which Wget recognizes, is using the following environment variables: -@table @code +@table @env @item http_proxy @itemx https_proxy -If set, the @code{http_proxy} and @code{https_proxy} variables should +If set, the @env{http_proxy} and @env{https_proxy} variables should contain the @sc{url}s of the proxies for @sc{http} and @sc{https} connections respectively. @item ftp_proxy This variable should contain the @sc{url} of the proxy for @sc{ftp} -connections. It is quite common that @code{http_proxy} and -@code{ftp_proxy} are set to the same @sc{url}. +connections. It is quite common that @env{http_proxy} and +@env{ftp_proxy} are set to the same @sc{url}. @item no_proxy This variable should contain a comma-separated list of domain extensions proxy should @emph{not} be used for. For instance, if the value of -@code{no_proxy} is @samp{.mit.edu}, proxy will not be used to retrieve +@env{no_proxy} is @samp{.mit.edu}, proxy will not be used to retrieve documents from MIT. @end table +@c man end In addition to the environment variables, proxy location and settings may be specified from within Wget itself. @table @samp -@itemx --no-proxy +@item --no-proxy @itemx proxy = on/off This option and the corresponding command may be used to suppress the use of proxy, even if the appropriate environment variables are set. @@ -3912,9 +4004,8 @@ me). GNU Wget was written by Hrvoje Nik@v{s}i@'{c} @email{hniksic@@xemacs.org}, @end iftex @ifnottex -GNU Wget was written by Hrvoje Niksic @email{hniksic@@xemacs.org}, +GNU Wget was written by Hrvoje Niksic @email{hniksic@@xemacs.org}. @end ifnottex -and it is currently maintained by Micah Cowan @email{micah@@cowan.name}. However, the development of Wget could never have gone as far as it has, were it not for the help of many people, either with bug reports, feature proposals,