X-Git-Url: http://sjero.net/git/?p=wget;a=blobdiff_plain;f=doc%2Fwget.texi;h=cced7edda118e268b6f290ae272380179044dbce;hp=288059ef378361b302ac7f948e3ab70b79ac0e37;hb=42c78fdd71c311cf96210b709ec0a18ef45ef87f;hpb=6c30653a1aad1dd2125122adfd477480cc9c9ca5 diff --git a/doc/wget.texi b/doc/wget.texi index 288059ef..cced7edd 100644 --- a/doc/wget.texi +++ b/doc/wget.texi @@ -550,10 +550,10 @@ IPs. @cindex retries @cindex tries -@cindex number of retries +@cindex number of tries @item -t @var{number} @itemx --tries=@var{number} -Set number of retries to @var{number}. Specify 0 or @samp{inf} for +Set number of tries to @var{number}. Specify 0 or @samp{inf} for infinite retrying. The default is to retry 20 times, with the exception of fatal errors like ``connection refused'' or ``not found'' (404), which are not retried. @@ -630,6 +630,13 @@ Note that when @samp{-nc} is specified, files with the suffixes @samp{.html} or @samp{.htm} will be loaded from the local disk and parsed as if they had been retrieved from the Web. +@cindex backing up files +@item --backups=@var{backups} +Before (over)writing a file, back up an existing file by adding a +@samp{.1} suffix (@samp{_1} on VMS) to the file name. Such backup +files are rotated to @samp{.2}, @samp{.3}, and so on, up to +@var{backups} (and lost beyond that). + @cindex continue retrieval @cindex incomplete downloads @cindex resume download @@ -715,9 +722,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 @@ -732,7 +742,7 @@ Turn on time-stamping. @xref{Time-Stamping}, for details. @item --no-use-server-timestamps Don't set the local file's timestamp by the one on the server. -By default, when a file is downloaded, it's timestamps are set to +By default, when a file is downloaded, its timestamps are set to match those from the remote file. This allows the use of @samp{--timestamping} on subsequent invocations of wget. However, it is sometimes useful to base the local file's timestamp on when it was @@ -1472,14 +1482,15 @@ use chunked unless it knows it's talking to an HTTP/1.1 server. And it can't know that until it receives a response, which in turn requires the request to have been completed -- a chicken-and-egg problem. -Note: if Wget is redirected after the POST request is completed, it -will not send the POST data to the redirected URL. This is because -URLs that process POST often respond with a redirection to a regular -page, which does not desire or accept POST. It is not completely -clear that this behavior is optimal; if it doesn't work out, it might -be changed in the future. +Note: As of version 1.15 if Wget is redirected after the POST request is +completed, its behaviour will depend on the response code returned by the +server. In case of a 301 Moved Permanently, 302 Moved Temporarily or +307 Temporary Redirect, Wget will, in accordance with RFC2616, continue +to send a POST request. +In case a server wants the client to change the Request method upon +redirection, it should send a 303 See Other response code. -This example shows how to log to a server using POST and then proceed to +This example shows how to log in to a server using POST and then proceed to download the desired pages, presumably only accessible to authorized users: @@ -1512,8 +1523,8 @@ 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, +Method specified using @samp{--method}. @samp{--body-data} sends @var{string} as +data, whereas @samp{--body-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. @@ -1525,10 +1536,13 @@ 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}. +If Wget is redirected after the request is completed, Wget will +suspend the current method and send a GET request till the redirection +is completed. This is true for all redirection response codes except +307 Temporary Redirect which is used to explicitly specify that the +request method should @emph{not} change. Another exception is when +the method is set to @code{POST}, in which case the redirection rules +specified under @samp{--post-data} are followed. @cindex Content-Disposition @item --content-disposition @@ -1592,6 +1606,9 @@ buggy SSL server implementations that make it hard for OpenSSL to choose the correct protocol version. Fortunately, such servers are quite rare. +@item --https-only +When in recursive mode, only HTTPS links are followed. + @cindex SSL certificate, check @item --no-check-certificate Don't check the server certificate against the available certificate @@ -1809,6 +1826,10 @@ in some rare firewall configurations, active FTP actually works when passive FTP doesn't. If you suspect this to be the case, use this option, or set @code{passive_ftp=off} in your init file. +@cindex file permissions +@item --preserve-permissions +Preserve remote file permissions instead of permissions set by umask. + @cindex symbolic links, retrieving @item --retr-symlinks Usually, when retrieving @sc{ftp} directories recursively and a symbolic @@ -2046,6 +2067,15 @@ any of the wildcard characters, @samp{*}, @samp{?}, @samp{[} or @samp{]}, appear in an element of @var{acclist} or @var{rejlist}, it will be treated as a pattern, rather than a suffix. +@item --accept-regex @var{urlregex} +@itemx --reject-regex @var{urlregex} +Specify a regular expression to accept or reject the complete URL. + +@item --regex-type @var{regextype} +Specify the regular expression type. Possible types are @samp{posix} or +@samp{pcre}. Note that to be able to use @samp{pcre} type, wget has to be +compiled with libpcre support. + @item -D @var{domain-list} @itemx --domains=@var{domain-list} Set domains to be followed. @var{domain-list} is a comma-separated list @@ -2862,9 +2892,11 @@ enables it). Enable/disable saving pre-converted files with the suffix @samp{.orig}---the same as @samp{-K} (which enables it). -@c @item backups = @var{number} -@c #### Document me! -@c +@item backups = @var{number} +Use up to @var{number} backups for a file. Backups are rotated by +adding an incremental counter that starts at @samp{1}. The default is +@samp{0}. + @item base = @var{string} Consider relative @sc{url}s in input files (specified via the @samp{input} command or the @samp{--input-file}/@samp{-i} option,