@c %**start of header
@setfilename wget.info
-@settitle GNU Wget Manual
+@include version.texi
+@set UPDATED May 2003
+@settitle GNU Wget @value{VERSION} Manual
@c Disable the monstrous rectangles beside overfull hbox-es.
@finalout
@c Use `odd' to print double-sided.
@set Wget Wget
@c man title Wget The non-interactive network downloader.
-@c This should really be generated automatically, possibly by including
-@c an auto-generated file.
-@set VERSION 1.9-cvs
-@set UPDATED September 2003
-
-@dircategory Net Utilities
-@dircategory World Wide Web
+@dircategory Network Applications
@direntry
* Wget: (wget). The non-interactive network downloader.
@end direntry
-@ifinfo
+@ifnottex
This file documents the the GNU Wget utility for downloading network
data.
Back-Cover Texts. A copy of the license is included in the section
entitled ``GNU Free Documentation License''.
@c man end
-@end ifinfo
+@end ifnottex
@titlepage
-@title GNU Wget
-@subtitle The noninteractive downloading utility
+@title GNU Wget @value{VERSION}
+@subtitle The non-interactive download utility
@subtitle Updated for Wget @value{VERSION}, @value{UPDATED}
@author by Hrvoje Nik@v{s}i@'{c} and the developers
@ignore
@c man begin AUTHOR
-Originally written by Hrvoje Niksic <hniksic@arsdigita.com>.
+Originally written by Hrvoje Niksic <hniksic@xemacs.org>.
@c man end
@c man begin SEEALSO
GNU Info entry for @file{wget}.
@page
@vskip 0pt plus 1filll
-Copyright @copyright{} 1996, 1997, 1998, 2000, 2001 Free Software
+Copyright @copyright{} 1996, 1997, 1998, 2000, 2001, 2003 Free Software
Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
-under the terms of the GNU Free Documentation License, Version 1.1 or
+under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with the
Invariant Sections being ``GNU General Public License'' and ``GNU Free
Documentation License'', with no Front-Cover Texts, and with no
entitled ``GNU Free Documentation License''.
@end titlepage
-@ifinfo
-@node Top, Overview, (dir), (dir)
+@ifnottex
+@node Top
@top Wget @value{VERSION}
This manual documents version @value{VERSION} of GNU Wget, the freely
-available utility for network download.
+available utility for network downloads.
-Copyright @copyright{} 1996, 1997, 1998, 2000, 2001 Free Software
+Copyright @copyright{} 1996, 1997, 1998, 2000, 2001, 2003 Free Software
Foundation, Inc.
@menu
* Overview:: Features of Wget.
* Invoking:: Wget command-line arguments.
-* Recursive Retrieval:: Description of recursive retrieval.
+* Recursive Download:: Downloading interlinked pages.
* Following Links:: The available methods of chasing links.
* Time-Stamping:: Mirroring according to time-stamps.
* Startup File:: Wget's initialization file.
* Copying:: You may give out copies of Wget and of this manual.
* Concept Index:: Topics covered by this manual.
@end menu
-@end ifinfo
+@end ifnottex
-@node Overview, Invoking, Top, Top
+@node Overview
@chapter Overview
@cindex overview
@cindex features
@c man end
@end ignore
@c man begin DESCRIPTION
-Wget can follow links in @sc{html} pages and create local versions of
-remote web sites, fully recreating the directory structure of the
-original site. This is sometimes referred to as ``recursive
+Wget can follow links in @sc{html} and @sc{xhtml} pages and create local
+versions of remote web sites, fully recreating the directory structure of
+the original site. This is sometimes referred to as ``recursive
downloading.'' While doing that, Wget respects the Robot Exclusion
Standard (@file{/robots.txt}). Wget can be instructed to convert the
links in downloaded @sc{html} files to the local files for offline
@sp 1
@item
-Builtin features offer mechanisms to tune which links you wish to follow
+Built-in features offer mechanisms to tune which links you wish to follow
(@pxref{Following Links}).
@sp 1
(@pxref{Copying}).
@end itemize
-@node Invoking, Recursive Retrieval, Overview, Top
+@node Invoking
@chapter Invoking
@cindex invoking
@cindex command line
* Recursive Accept/Reject Options::
@end menu
-@node URL Format, Option Syntax, Invoking, Invoking
+@node URL Format
@section URL Format
@cindex URL
@cindex URL syntax
not know which one to use, just use the plain ordinary format you use
with your favorite browser, like @code{Lynx} or @code{Netscape}.
-@node Option Syntax, Basic Startup Options, URL Format, Invoking
+@node Option Syntax
@section Option Syntax
@cindex option syntax
@cindex syntax of options
@c man begin OPTIONS
-@node Basic Startup Options, Logging and Input File Options, Option Syntax, Invoking
+@node Basic Startup Options
@section Basic Startup Options
@table @samp
them.
@end table
-@node Logging and Input File Options, Download Options, Basic Startup Options, Invoking
+@node Logging and Input File Options
@section Logging and Input File Options
@table @samp
links in the file specified by @samp{-i}.
@end table
-@node Download Options, Directory Options, Logging and Input File Options, Invoking
+@node Download Options
@section Download Options
@table @samp
The documents will not be written to the appropriate files, but all will
be concatenated together and written to @var{file}. If @var{file}
already exists, it will be overwritten. If the @var{file} is @samp{-},
-the documents will be written to standard output. Including this option
-automatically sets the number of tries to 1.
+the documents will be written to standard output.
@cindex clobbering, file
@cindex downloading multiple times
time as @samp{-N}.
Note that when @samp{-nc} is specified, files with the suffixes
-@samp{.html} or (yuck) @samp{.htm} will be loaded from the local disk
-and parsed as if they had been retrieved from the Web.
+@samp{.html} or @samp{.htm} will be loaded from the local disk and
+parsed as if they had been retrieved from the Web.
@cindex continue retrieval
@cindex incomplete downloads
Select the type of the progress indicator you wish to use. Legal
indicators are ``dot'' and ``bar''.
-The ``bar'' indicator is used by default. It draws an ASCII progress
+The ``bar'' indicator is used by default. It draws an @sc{ascii} progress
bar graphics (a.k.a ``thermometer'' display) indicating the status of
retrieval. If the output is not a TTY, the ``dot'' bar will be used by
default.
@item --spider
When invoked with this option, Wget will behave as a Web @dfn{spider},
which means that it will not download the pages, just check that they
-are there. You can use it to check your bookmarks, e.g. with:
+are there. For example, you can use Wget to check your bookmarks:
@example
wget --spider --force-html -i bookmarks.html
@end example
This feature needs much more work for Wget to get close to the
-functionality of real @sc{www} spiders.
+functionality of real web spiders.
@cindex timeout
@item -T seconds
@itemx --timeout=@var{seconds}
-Set the network timeout to @var{seconds} seconds. Whenever Wget
-connects to or reads from a remote host, it checks for a timeout and
-aborts the operation if the time expires. This prevents anomalous
-occurrences such as hanging reads or infinite connects. The default
-timeout is 900 seconds (fifteen minutes). Setting timeout to 0 will
-disable checking for timeouts.
-
-Please do not lower the default timeout value with this option unless
-you know what you are doing.
+Set the network timeout to @var{seconds} seconds. This is equivalent
+to specifying @samp{--dns-timeout}, @samp{--connect-timeout}, and
+@samp{--read-timeout}, all at the same time.
+
+Whenever Wget connects to or reads from a remote host, it checks for a
+timeout and aborts the operation if the time expires. This prevents
+anomalous occurrences such as hanging reads or infinite connects. The
+only timeout enabled by default is a 900-second timeout for reading.
+Setting timeout to 0 disables checking for timeouts.
+
+Unless you know what you are doing, it is best not to set any of the
+timeout-related options.
+
+@cindex DNS timeout
+@cindex timeout, DNS
+@item --dns-timeout=@var{seconds}
+Set the DNS lookup timeout to @var{seconds} seconds. DNS lookups that
+don't complete within the specified time will fail. By default, there
+is no timeout on DNS lookups, other than that implemented by system
+libraries.
+
+@cindex connect timeout
+@cindex timeout, connect
+@item --connect-timeout=@var{seconds}
+Set the connect timeout to @var{seconds} seconds. TCP connections that
+take longer to establish will be aborted. By default, there is no
+connect timeout, other than that implemented by system libraries.
+
+@cindex read timeout
+@cindex timeout, read
+@item --read-timeout=@var{seconds}
+Set the read (and write) timeout to @var{seconds} seconds. Reads that
+take longer will fail. The default value for read timeout is 900
+seconds.
@cindex bandwidth, limit
@cindex rate, limit
Note that Wget implements the limiting by sleeping the appropriate
amount of time after a network read that took less time than specified
by the rate. Eventually this strategy causes the TCP transfer to slow
-down to approximately the specified rate. However, it takes some time
-for this balance to be achieved, so don't be surprised if limiting the
-rate doesn't work well with very small files.
+down to approximately the specified rate. However, it may take some
+time for this balance to be achieved, so don't be surprised if limiting
+the rate doesn't work well with very small files.
@cindex pause
@cindex wait
such as Wget by looking for statistically significant similarities in
the time between requests. This option causes the time between requests
to vary between 0 and 2 * @var{wait} seconds, where @var{wait} was
-specified using the @samp{-w} or @samp{--wait} options, in order to mask
-Wget's presence from such analysis.
+specified using the @samp{--wait} option, in order to mask Wget's
+presence from such analysis.
A recent article in a publication devoted to development on a popular
consumer platform provided code to perform this analysis on the fly.
the control characters in the ranges 0--31 and 128--159. This is the
default on Unix-like OS'es.
-When mode is seto to ``windows'', Wget escapes the characters @samp{\},
+When mode is set to ``windows'', Wget escapes the characters @samp{\},
@samp{|}, @samp{/}, @samp{:}, @samp{?}, @samp{"}, @samp{*}, @samp{<},
@samp{>}, and the control characters in the ranges 0--31 and 128--159.
In addition to this, Wget in Windows mode uses @samp{+} instead of
the OS to use as file name restriction mode.
@end table
-@node Directory Options, HTTP Options, Download Options, Invoking
+@node Directory Options
@section Directory Options
@table @samp
directories beginning with @file{fly.srk.fer.hr/}. This option disables
such behavior.
+@item --protocol-directories
+Use the protocol name as a directory component of local file names. For
+example, with this option, @samp{wget -r http://@var{host}} will save to
+@samp{http/@var{host}/...} rather than just to @samp{@var{host}/...}.
+
+Disable generation of host-prefixed directories. By default, invoking
+Wget with @samp{-r http://fly.srk.fer.hr/} will create a structure of
+directories beginning with @file{fly.srk.fer.hr/}. This option disables
+such behavior.
+
@cindex cut directories
@item --cut-dirs=@var{number}
Ignore @var{number} directory components. This is useful for getting a
current directory).
@end table
-@node HTTP Options, FTP Options, Directory Options, Invoking
+@node HTTP Options
@section HTTP Options
@table @samp
@cindex .html extension
@item -E
@itemx --html-extension
-If a file of type @samp{text/html} is downloaded and the URL does not
-end with the regexp @samp{\.[Hh][Tt][Mm][Ll]?}, this option will cause
-the suffix @samp{.html} to be appended to the local filename. This is
-useful, for instance, when you're mirroring a remote site that uses
-@samp{.asp} pages, but you want the mirrored pages to be viewable on
-your stock Apache server. Another good use for this is when you're
-downloading the output of CGIs. A URL like
-@samp{http://site.com/article.cgi?25} will be saved as
+If a file of type @samp{application/xhtml+xml} or @samp{text/html} is
+downloaded and the URL does not end with the regexp
+@samp{\.[Hh][Tt][Mm][Ll]?}, this option will cause the suffix @samp{.html}
+to be appended to the local filename. This is useful, for instance, when
+you're mirroring a remote site that uses @samp{.asp} pages, but you want
+the mirrored pages to be viewable on your stock Apache server. Another
+good use for this is when you're downloading CGI-generated materials. A URL
+like @samp{http://site.com/article.cgi?25} will be saved as
@file{article.cgi?25.html}.
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}. 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}. 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}).
@cindex http user
@cindex http password
@cindex proxy
@cindex cache
-@item -C on/off
-@itemx --cache=on/off
-When set to off, disable server-side cache. In this case, Wget will
-send the remote server an appropriate directive (@samp{Pragma:
-no-cache}) to get the file from the remote service, rather than
-returning the cached version. This is especially useful for retrieving
-and flushing out-of-date documents on proxy servers.
+@item --no-cache
+Disable server-side cache. In this case, Wget will send the remote
+server an appropriate directive (@samp{Pragma: no-cache}) to get the
+file from the remote service, rather than returning the cached version.
+This is especially useful for retrieving and flushing out-of-date
+documents on proxy servers.
Caching is allowed by default.
@cindex cookies
-@item --cookies=on/off
-When set to off, disable the use of cookies. Cookies are a mechanism
-for maintaining server-side state. The server sends the client a cookie
-using the @code{Set-Cookie} header, and the client responds with the
-same cookie upon further requests. Since cookies allow the server
-owners to keep track of visitors and for sites to exchange this
-information, some consider them a breach of privacy. The default is to
-use cookies; however, @emph{storing} cookies is not on by default.
+@item --no-cookies
+Disable the use of cookies. Cookies are a mechanism for maintaining
+server-side state. The server sends the client a cookie using the
+@code{Set-Cookie} header, and the client responds with the same cookie
+upon further requests. Since cookies allow the server owners to keep
+track of visitors and for sites to exchange this information, some
+consider them a breach of privacy. The default is to use cookies;
+however, @emph{storing} cookies is not on by default.
@cindex loading cookies
@cindex cookies, loading
@cindex saving cookies
@cindex cookies, saving
@item --save-cookies @var{file}
-Save cookies from @var{file} at the end of session. Cookies whose
-expiry time is not specified, or those that have already expired, are
-not saved.
+Save cookies to @var{file} before exiting. This will not save cookies
+that have expired or that have no expiry time (so-called ``session
+cookies''), but also see @samp{--keep-session-cookies}.
+
+@cindex cookies, session
+@cindex session cookies
+@item --keep-session-cookies
+
+When specified, causes @samp{--save-cookies} to also save session
+cookies. Session cookies are normally not save because they are
+supposed to be forgotten when you exit the browser. Saving them is
+useful on sites that require you to log in or to visit the home page
+before you can access some pages. With this option, multiple Wget runs
+are considered a single browser session as far as the site is concerned.
+
+Since the cookie file format does not normally carry session cookies,
+Wget marks them with an expiry timestamp of 0. Wget's
+@samp{--load-cookies} recognizes those as session cookies, but it might
+confuse other browsers. Also note that cookies so loaded will be
+treated as other session cookies, which means that if you want
+@samp{--save-cookies} to preserve them again, you must use
+@samp{--keep-session-cookies} again.
@cindex Content-Length, ignore
@cindex ignore length
properly when Referer is set to one of the pages that point to them.
@cindex server response, save
-@item -s
-@itemx --save-headers
+@item --save-headers
Save the headers sent by the @sc{http} server to the file, preceding the
actual contents, with an empty line as the separator.
Microsoft @code{Internet Explorer}. This option allows you to change
the @code{User-Agent} line issued by Wget. Use of this option is
discouraged, unless you really know what you are doing.
+
+@cindex POST
+@item --post-data=@var{string}
+@itemx --post-file=@var{file}
+Use POST as the method for all HTTP requests and send the specified data
+in the request body. @code{--post-data} sends @var{string} as data,
+whereas @code{--post-file} sends the contents of @var{file}. Other than
+that, they work in exactly the same way.
+
+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.
+It's not quite clear how to work around this limitation inherent in
+HTTP/1.0. Although HTTP/1.1 introduces @dfn{chunked} transfer that
+doesn't require knowing the request length in advance, a client can't
+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
+(although that's technically disallowed), which does not desire or
+accept POST. It is not yet clear that this behavior is optimal; if it
+doesn't work out, it will be changed.
+
+This example shows how to log to a server using POST and then proceed to
+download the desired pages, presumably only accessible to authorized
+users:
+
+@example
+@group
+# @r{Log in to the server. This can be done only once.}
+wget --save-cookies cookies.txt \
+ --post-data 'user=foo&password=bar' \
+ http://server.com/auth.php
+
+# @r{Now grab the page or pages we care about.}
+wget --load-cookies cookies.txt \
+ -p http://server.com/interesting/article.php
+@end group
+@end example
@end table
-@node FTP Options, Recursive Retrieval Options, HTTP Options, Invoking
+@node FTP Options
@section FTP Options
@table @samp
@cindex .listing files, removing
-@item -nr
-@itemx --dont-remove-listing
+@item --no-remove-listing
Don't remove the temporary @file{.listing} files generated by @sc{ftp}
retrievals. Normally, these files contain the raw directory listings
received from @sc{ftp} servers. Not removing them can be useful for
will be overwritten.
@cindex globbing, toggle
-@item -g on/off
-@itemx --glob=on/off
-Turn @sc{ftp} globbing on or off. Globbing means you may use the
-shell-like special characters (@dfn{wildcards}), like @samp{*},
-@samp{?}, @samp{[} and @samp{]} to retrieve more than one file from the
-same directory at once, like:
+@item --no-glob
+Turn off @sc{ftp} globbing. Globbing refers to the use of shell-like
+special characters (@dfn{wildcards}), like @samp{*}, @samp{?}, @samp{[}
+and @samp{]} to retrieve more than one file from the same directory at
+once, like:
@example
wget ftp://gnjilux.srk.fer.hr/*.msg
this.
Note that when retrieving a file (not a directory) because it was
-specified on the commandline, rather than because it was recursed to,
+specified on the command-line, rather than because it was recursed to,
this option has no effect. Symbolic links are always traversed in this
case.
@end table
-@node Recursive Retrieval Options, Recursive Accept/Reject Options, FTP Options, Invoking
+@node Recursive Retrieval Options
@section Recursive Retrieval Options
@table @samp
@item -r
@itemx --recursive
-Turn on recursive retrieving. @xref{Recursive Retrieval}, for more
+Turn on recursive retrieving. @xref{Recursive Download}, for more
details.
@item -l @var{depth}
@itemx --level=@var{depth}
Specify recursion maximum depth level @var{depth} (@pxref{Recursive
-Retrieval}). The default maximum depth is 5.
+Download}). The default maximum depth is 5.
@cindex proxy filling
@cindex delete after retrieval
After the download is complete, convert the links in the document to
make them suitable for local viewing. This affects not only the visible
hyperlinks, but any part of the document that links to external content,
-such as embedded images, links to style sheets, hyperlinks to non-HTML
+such as embedded images, links to style sheets, hyperlinks to non-@sc{html}
content, etc.
Each link will be changed in one of the two ways:
Turn on options suitable for mirroring. This option turns on recursion
and time-stamping, sets infinite recursion depth and keeps @sc{ftp}
directory listings. It is currently equivalent to
-@samp{-r -N -l inf -nr}.
+@samp{-r -N -l inf --no-remove-listing}.
@cindex page requisites
@cindex required images, downloading
@item -p
@itemx --page-requisites
This option causes Wget to download all the files that are necessary to
-properly display a given HTML page. This includes such things as
+properly display a given @sc{html} page. This includes such things as
inlined images, sounds, and referenced stylesheets.
-Ordinarily, when downloading a single HTML page, any requisite documents
+Ordinarily, when downloading a single @sc{html} page, any requisite documents
that may be needed to display it properly are not downloaded. Using
@samp{-r} together with @samp{-l} can help, but since Wget does not
ordinarily distinguish between external and inlined documents, one is
would download just @file{1.html} and @file{1.gif}, but unfortunately
this is not the case, because @samp{-l 0} is equivalent to
-@samp{-l inf}---that is, infinite recursion. To download a single HTML
-page (or a handful of them, all specified on the commandline or in a
+@samp{-l inf}---that is, infinite recursion. To download a single @sc{html}
+page (or a handful of them, all specified on the command-line or in a
@samp{-i} @sc{url} input file) and its (or their) requisites, simply leave off
@samp{-r} and @samp{-l}:
external document link is any URL specified in an @code{<A>} tag, an
@code{<AREA>} tag, or a @code{<LINK>} tag other than @code{<LINK
REL="stylesheet">}.
+
+@cindex @sc{html} comments
+@cindex comments, @sc{html}
+@item --strict-comments
+Turn on strict parsing of @sc{html} comments. The default is to terminate
+comments at the first occurrence of @samp{-->}.
+
+According to specifications, @sc{html} comments are expressed as @sc{sgml}
+@dfn{declarations}. Declaration is special markup that begins with
+@samp{<!} and ends with @samp{>}, such as @samp{<!DOCTYPE ...>}, that
+may contain comments between a pair of @samp{--} delimiters. @sc{html}
+comments are ``empty declarations'', @sc{sgml} declarations without any
+non-comment text. Therefore, @samp{<!--foo-->} is a valid comment, and
+so is @samp{<!--one-- --two-->}, but @samp{<!--1--2-->} is not.
+
+On the other hand, most @sc{html} writers don't perceive comments as anything
+other than text delimited with @samp{<!--} and @samp{-->}, which is not
+quite the same. For example, something like @samp{<!------------>}
+works as a valid comment as long as the number of dashes is a multiple
+of four (!). If not, the comment technically lasts until the next
+@samp{--}, which may be at the other end of the document. Because of
+this, many popular browsers completely ignore the specification and
+implement what users have come to expect: comments delimited with
+@samp{<!--} and @samp{-->}.
+
+Until version 1.9, Wget interpreted comments strictly, which resulted in
+missing links in many web pages that displayed fine in browsers, but had
+the misfortune of containing non-compliant comments. Beginning with
+version 1.9, Wget has joined the ranks of clients that implements
+``naive'' comments, terminating each comment at the first occurrence of
+@samp{-->}.
+
+If, for whatever reason, you want strict comment parsing, use this
+option to turn it on.
@end table
-@node Recursive Accept/Reject Options, , Recursive Retrieval Options, Invoking
+@node Recursive Accept/Reject Options
@section Recursive Accept/Reject Options
@table @samp
@cindex tag-based recursive pruning
@item --follow-tags=@var{list}
-Wget has an internal table of HTML tag / attribute pairs that it
+Wget has an internal table of @sc{html} tag / attribute pairs that it
considers when looking for linked documents during a recursive
retrieval. If a user wants only a subset of those tags to be
considered, however, he or she should be specify such tags in a
comma-separated @var{list} with this option.
-@item -G @var{list}
-@itemx --ignore-tags=@var{list}
+@item --ignore-tags=@var{list}
This is the opposite of the @samp{--follow-tags} option. To skip
-certain HTML tags when recursively looking for documents to download,
+certain @sc{html} tags when recursively looking for documents to download,
specify them in a comma-separated @var{list}.
-In the past, the @samp{-G} option was the best bet for downloading a
-single page and its requisites, using a commandline like:
+In the past, this option was the best bet for downloading a single page
+and its requisites, using a command-line like:
@example
-wget -Ga,area -H -k -K -r http://@var{site}/@var{document}
+wget --ignore-tags=a,area -H -k -K -r http://@var{site}/@var{document}
@end example
However, the author of this option came across a page with tags like
@code{<LINK REL="home" HREF="/">} and came to the realization that
-@samp{-G} was not enough. One can't just tell Wget to ignore
-@code{<LINK>}, because then stylesheets will not be downloaded. Now the
-best bet for downloading a single page and its requisites is the
+specifying tags to ignore was not enough. One can't just tell Wget to
+ignore @code{<LINK>}, because then stylesheets will not be downloaded.
+Now the best bet for downloading a single page and its requisites is the
dedicated @samp{--page-requisites} option.
@item -H
@c man end
-@node Recursive Retrieval, Following Links, Invoking, Top
-@chapter Recursive Retrieval
+@node Recursive Download
+@chapter Recursive Download
@cindex recursion
@cindex retrieving
-@cindex recursive retrieval
+@cindex recursive download
GNU Wget is capable of traversing parts of the Web (or a single
@sc{http} or @sc{ftp} server), following links and directory structure.
-We refer to this as to @dfn{recursive retrieving}, or @dfn{recursion}.
+We refer to this as to @dfn{recursive retrieval}, or @dfn{recursion}.
With @sc{http} @sc{url}s, Wget retrieves and parses the @sc{html} from
the given @sc{url}, documents, retrieving the files the @sc{html}
-document was referring to, through markups like @code{href}, or
+document was referring to, through markup like @code{href}, or
@code{src}. If the freshly downloaded file is also of type
-@code{text/html}, it will be parsed and followed further.
+@code{text/html} or @code{application/xhtml+xml}, it will be parsed and
+followed further.
Recursive retrieval of @sc{http} and @sc{html} content is
@dfn{breadth-first}. This means that Wget first downloads the requested
-HTML document, then the documents linked from that document, then the
+@sc{html} document, then the documents linked from that document, then the
documents linked by them, and so on. In other words, Wget first
downloads the documents at depth 1, then those at depth 2, and so on
until the specified maximum depth.
Recursive retrieval should be used with care. Don't say you were not
warned.
-@node Following Links, Time-Stamping, Recursive Retrieval, Top
+@node Following Links
@chapter Following Links
@cindex links
@cindex following links
* FTP Links:: Following FTP links.
@end menu
-@node Spanning Hosts, Types of Files, Following Links, Following Links
+@node Spanning Hosts
@section Spanning Hosts
@cindex spanning hosts
@cindex hosts, spanning
However, visiting different hosts, or @dfn{host spanning,} is sometimes
a useful option. Maybe the images are served from a different server.
Maybe you're mirroring a site that consists of pages interlinked between
-three servers. Maybe the server has two equivalent names, and the HTML
+three servers. Maybe the server has two equivalent names, and the @sc{html}
pages refer to both interchangeably.
@table @asis
@end table
-@node Types of Files, Directory-Based Limits, Spanning Hosts, Following Links
+@node Types of Files
@section Types of Files
@cindex types of files
files; Wget must load all the @sc{html}s to know where to go at
all---recursive retrieval would make no sense otherwise.
-@node Directory-Based Limits, Relative Links, Types of Files, Following Links
+@node Directory-Based Limits
@section Directory-Based Limits
@cindex directories
@cindex directory limits
intelligent fashion.
@end table
-@node Relative Links, FTP Links, Directory-Based Limits, Following Links
+@node Relative Links
@section Relative Links
@cindex relative links
This option is probably not very useful and might be removed in a future
release.
-@node FTP Links, , Relative Links, Following Links
+@node FTP Links
@section Following FTP Links
@cindex following ftp links
Also note that followed links to @sc{ftp} directories will not be
retrieved recursively further.
-@node Time-Stamping, Startup File, Following Links, Top
+@node Time-Stamping
@chapter Time-Stamping
@cindex time-stamping
@cindex timestamping
* FTP Time-Stamping Internals::
@end menu
-@node Time-Stamping Usage, HTTP Time-Stamping Internals, Time-Stamping, Time-Stamping
+@node Time-Stamping Usage
@section Time-Stamping Usage
@cindex time-stamping usage
@cindex usage, time-stamping
directory listing with dates in a format that Wget can parse
(@pxref{FTP Time-Stamping Internals}).
-@node HTTP Time-Stamping Internals, FTP Time-Stamping Internals, Time-Stamping Usage, Time-Stamping
+@node HTTP Time-Stamping Internals
@section HTTP Time-Stamping Internals
@cindex http time-stamping
Arguably, @sc{http} time-stamping should be implemented using the
@code{If-Modified-Since} request.
-@node FTP Time-Stamping Internals, , HTTP Time-Stamping Internals, Time-Stamping
+@node FTP Time-Stamping Internals
@section FTP Time-Stamping Internals
@cindex ftp time-stamping
@code{wu-ftpd}), which returns the exact time of the specified file.
Wget may support this command in the future.
-@node Startup File, Examples, Time-Stamping, Top
+@node Startup File
@chapter Startup File
@cindex startup file
@cindex wgetrc
* Sample Wgetrc:: A wgetrc example.
@end menu
-@node Wgetrc Location, Wgetrc Syntax, Startup File, Startup File
+@node Wgetrc Location
@section Wgetrc Location
@cindex wgetrc location
@cindex location of wgetrc
system-wide wgetrc (in @file{/usr/local/etc/wgetrc} by default).
Fascist admins, away!
-@node Wgetrc Syntax, Wgetrc Commands, Wgetrc Location, Startup File
+@node Wgetrc Syntax
@section Wgetrc Syntax
@cindex wgetrc syntax
@cindex syntax of wgetrc
reject =
@end example
-@node Wgetrc Commands, Sample Wgetrc, Wgetrc Syntax, Startup File
+@node Wgetrc Commands
@section Wgetrc Commands
@cindex wgetrc commands
Boolean allowed in some cases is the @dfn{lockable Boolean}, which may
be set to @samp{on}, @samp{off}, @samp{always}, or @samp{never}. If an
option is set to @samp{always} or @samp{never}, that value will be
-locked in for the duration of the Wget invocation---commandline options
+locked in for the duration of the Wget invocation---command-line options
will not override.
Some commands take pseudo-arbitrary values. @var{address} values can be
integer, or @samp{inf} for infinity, where appropriate. @var{string}
values can be any non-empty string.
-Most of these commands have commandline equivalents (@pxref{Invoking}),
+Most of these commands have command-line equivalents (@pxref{Invoking}),
though some of the more obscure or rarely used ones do not.
@table @asis
Bind to @var{address}, like the @samp{--bind-address} option.
@item cache = on/off
-When set to off, disallow server-caching. See the @samp{-C} option.
+When set to off, disallow server-caching. See the @samp{--no-cache}
+option.
-@item convert links = on/off
+@item convert_links = on/off
Convert non-relative links locally. The same as @samp{-k}.
@item cookies = on/off
@item save_cookies = @var{file}
Save cookies to @var{file}. See @samp{--save-cookies}.
+@item connect_timeout = @var{n}
+Set the connect timeout---the same as @samp{--connect-timeout}.
+
@item cut_dirs = @var{n}
Ignore @var{n} remote directory components.
Turn DNS caching on/off. Since DNS caching is on by default, this
option is normally used to turn it off. Same as @samp{--dns-cache}.
+@item dns_timeout = @var{n}
+Set the DNS timeout---the same as @samp{--dns-timeout}.
+
@item domains = @var{string}
Same as @samp{-D} (@pxref{Spanning Hosts}).
@samp{--follow-ftp}.
@item follow_tags = @var{string}
-Only follow certain HTML tags when doing a recursive retrieval, just like
+Only follow certain @sc{html} tags when doing a recursive retrieval, just like
@samp{--follow-tags}.
@item force_html = on/off
environment.
@item glob = on/off
-Turn globbing on/off---the same as @samp{-g}.
+Turn globbing on/off---the same as @samp{--glob} and @samp{--no-glob}.
@item header = @var{string}
Define an additional header, like @samp{--header}.
@item html_extension = on/off
-Add a @samp{.html} extension to @samp{text/html} files without it, like
+Add a @samp{.html} extension to @samp{text/html} or
+@samp{application/xhtml+xml} files without it, like
@samp{-E}.
@item http_passwd = @var{string}
@samp{--ignore-length}.
@item ignore_tags = @var{string}
-Ignore certain HTML tags when doing a recursive retrieval, just like
-@samp{-G} / @samp{--ignore-tags}.
+Ignore certain @sc{html} tags when doing a recursive retrieval, just like
+@samp{--ignore-tags}.
@item include_directories = @var{string}
Specify a comma-separated list of directories you wish to follow when
@item kill_longer = on/off
Consider data longer than specified in content-length header as invalid
-(and retry getting it). The default behaviour is to save as much data
+(and retry getting it). The default behavior is to save as much data
as there is, provided there is more than or equal to the value in
@code{Content-Length}.
Set the output filename---the same as @samp{-O}.
@item page_requisites = on/off
-Download all ancillary documents necessary for a single HTML page to
+Download all ancillary documents necessary for a single @sc{html} page to
display properly---the same as @samp{-p}.
@item passive_ftp = on/off/always/never
Set passive @sc{ftp}---the same as @samp{--passive-ftp}. Some scripts
and @samp{.pm} (Perl module) files download files using @samp{wget
--passive-ftp}. If your firewall does not allow this, you can set
-@samp{passive_ftp = never} to override the commandline.
+@samp{passive_ftp = never} to override the command-line.
@item passwd = @var{string}
Set your @sc{ftp} password to @var{password}. Without this setting, the
password defaults to @samp{username@@hostname.domainname}.
+@item post_data = @var{string}
+Use POST as the method for all HTTP requests and send @var{string} in
+the request body. The same as @samp{--post-data}.
+
+@item post_file = @var{file}
+Use POST as the method for all HTTP requests and send the contents of
+@var{file} in the request body. The same as @samp{--post-file}.
+
@item progress = @var{string}
Set the type of the progress indicator. Legal types are ``dot'' and
``bar''.
+@item protocol_directories = on/off
+When set, use the protocol name as a directory component of local file
+names. The same as @samp{--protocol-directories}.
+
@item proxy_user = @var{string}
Set proxy authentication user name to @var{string}, like @samp{--proxy-user}.
to 5 mbytes. Note that the user's startup file overrides system
settings.
+@item read_timeout = @var{n}
+Set the read (and write) timeout---the same as @samp{--read-timeout}.
+
@item reclevel = @var{n}
Recursion level---the same as @samp{-l}.
@item remove_listing = on/off
If set to on, remove @sc{ftp} listings downloaded by Wget. Setting it
-to off is the same as @samp{-nr}.
+to off is the same as @samp{--no-remove-listing}.
@item restrict_file_names = unix/windows
Restrict the file names generated by Wget from URLs. See
@item span_hosts = on/off
Same as @samp{-H}.
+@item strict_comments = on/off
+Same as @samp{--strict-comments}.
+
@item timeout = @var{n}
Set timeout value---the same as @samp{-T}.
@samp{--random-wait}.
@end table
-@node Sample Wgetrc, , Wgetrc Commands, Startup File
+@node Sample Wgetrc
@section Sample Wgetrc
@cindex sample wgetrc
@include sample.wgetrc.munged_for_texi_inclusion
@end example
-@node Examples, Various, Startup File, Top
+@node Examples
@chapter Examples
@cindex examples
* Very Advanced Usage:: The hairy stuff.
@end menu
-@node Simple Usage, Advanced Usage, Examples, Examples
+@node Simple Usage
@section Simple Usage
@itemize @bullet
parse it and convert it to @sc{html}. Try:
@example
-wget ftp://prep.ai.mit.edu/pub/gnu/
+wget ftp://ftp.gnu.org/pub/gnu/
links index.html
@end example
@end itemize
-@node Advanced Usage, Very Advanced Usage, Simple Usage, Examples
+@node Advanced Usage
@section Advanced Usage
@itemize @bullet
@end example
@item
-Retrieve only one HTML page, but make sure that all the elements needed
+Retrieve only one @sc{html} page, but make sure that all the elements needed
for the page to be displayed, such as inline images and external style
sheets, are also downloaded. Also make sure the downloaded page
references the downloaded links.
wget -p --convert-links http://www.server.com/dir/page.html
@end example
-The HTML page will be saved to @file{www.server.com/dir/page.html}, and
+The @sc{html} page will be saved to @file{www.server.com/dir/page.html}, and
the images, stylesheets, etc., somewhere under @file{www.server.com/},
depending on where they were on the remote server.
@end example
More verbose, but the effect is the same. @samp{-r -l1} means to
-retrieve recursively (@pxref{Recursive Retrieval}), with maximum depth
+retrieve recursively (@pxref{Recursive Download}), with maximum depth
of 1. @samp{--no-parent} means that references to the parent directory
are ignored (@pxref{Directory-Based Limits}), and @samp{-A.gif} means to
download only the @sc{gif} files. @samp{-A "*.gif"} would have worked
@end example
@end itemize
-@node Very Advanced Usage, , Advanced Usage, Examples
+@node Very Advanced Usage
@section Very Advanced Usage
@cindex mirroring
In addition to the above, you want the links to be converted for local
viewing. But, after having read this manual, you know that link
conversion doesn't play well with timestamping, so you also want Wget to
-back up the original HTML files before the conversion. Wget invocation
+back up the original @sc{html} files before the conversion. Wget invocation
would look like this:
@example
@item
But you've also noticed that local viewing doesn't work all that well
-when HTML files are saved under extensions other than @samp{.html},
+when @sc{html} files are saved under extensions other than @samp{.html},
perhaps because they were served as @file{index.cgi}. So you'd like
Wget to rename all the files served with content-type @samp{text/html}
-to @file{@var{name}.html}.
+or @samp{application/xhtml+xml} to @file{@var{name}.html}.
@example
wget --mirror --convert-links --backup-converted \
@end itemize
@c man end
-@node Various, Appendices, Examples, Top
+@node Various
@chapter Various
@cindex various
* Signals:: Signal-handling performed by Wget.
@end menu
-@node Proxies, Distribution, Various, Various
+@node Proxies
@section Proxies
@cindex proxies
settings @code{proxy_user} and @code{proxy_passwd} to set the proxy
username and password.
-@node Distribution, Mailing List, Proxies, Various
+@node Distribution
@section Distribution
@cindex latest version
Like all GNU utilities, the latest version of Wget can be found at the
-master GNU archive site prep.ai.mit.edu, and its mirrors. For example,
+master GNU archive site ftp.gnu.org, and its mirrors. For example,
Wget @value{VERSION} can be found at
-@url{ftp://prep.ai.mit.edu/gnu/wget/wget-@value{VERSION}.tar.gz}
+@url{ftp://ftp.gnu.org/pub/gnu/wget/wget-@value{VERSION}.tar.gz}
-@node Mailing List, Reporting Bugs, Distribution, Various
+@node Mailing List
@section Mailing List
@cindex mailing list
@cindex list
interest to the public) and mailing announcements. You are welcome to
subscribe. The more people on the list, the better!
-To subscribe, send mail to @email{wget-subscribe@@sunsite.dk}.
-the magic word @samp{subscribe} in the subject line. Unsubscribe by
-mailing to @email{wget-unsubscribe@@sunsite.dk}.
+To subscribe, simply send mail to @email{wget-subscribe@@sunsite.dk}.
+Unsubscribe by mailing to @email{wget-unsubscribe@@sunsite.dk}.
The mailing list is archived at @url{http://fly.srk.fer.hr/archive/wget}.
Alternative archive is available at
@url{http://www.mail-archive.com/wget%40sunsite.auc.dk/}.
-@node Reporting Bugs, Portability, Mailing List, Various
+@node Reporting Bugs
@section Reporting Bugs
@cindex bugs
@cindex reporting bugs
@enumerate
@item
-Please try to ascertain that the behaviour you see really is a bug. If
+Please try to ascertain that the behavior you see really is a bug. If
Wget crashes, it's a bug. If Wget does not behave as documented,
it's a bug. If things work strange, but you are not sure about the way
they are supposed to work, it might well be a bug.
@end enumerate
@c man end
-@node Portability, Signals, Reporting Bugs, Various
+@node Portability
@section Portability
@cindex portability
@cindex operating systems
-Since Wget uses GNU Autoconf for building and configuring, and avoids
-using ``special'' ultra--mega--cool features of any particular Unix, it
-should compile (and work) on all common Unix flavors.
+Like all GNU software, Wget works on the GNU system. However, since it
+uses GNU Autoconf for building and configuring, and mostly avoids using
+``special'' features of any particular Unix, it should compile (and
+work) on all common Unix flavors.
Various Wget versions have been compiled and tested under many kinds of
-Unix systems, including Solaris, Linux, SunOS, OSF (aka Digital Unix),
-Ultrix, *BSD, IRIX, and others; refer to the file @file{MACHINES} in the
-distribution directory for a comprehensive list. If you compile it on
-an architecture not listed there, please let me know so I can update it.
+Unix systems, including Solaris, GNU/Linux, SunOS, OSF (aka Digital Unix
+or Tru64), Ultrix, *BSD, IRIX, AIX, and others; refer to the file
+@file{MACHINES} in the distribution directory for a comprehensive list.
+If you compile it on an architecture not listed there, please let me
+know so I can update it.
Wget should also compile on the other Unix systems, not listed in
@file{MACHINES}. If it doesn't, please let me know.
Thanks to kind contributors, this version of Wget compiles and works on
Microsoft Windows 95 and Windows NT platforms. It has been compiled
-successfully using MS Visual C++ 4.0, Watcom, and Borland C compilers,
+successfully using MS Visual C++ 6.0, Watcom, and Borland C compilers,
with Winsock as networking software. Naturally, it is crippled of some
features available on Unix, but it should work as a substitute for
people stuck with Windows. Note that the Windows port is
@strong{neither tested nor maintained} by me---all questions and
-problems should be reported to Wget mailing list at
-@email{wget@@sunsite.dk} where the maintainers will look at them.
+problems in Windows usage should be reported to Wget mailing list at
+@email{wget@@sunsite.dk} where the volunteers who maintain the
+Windows-related features might look at them.
-@node Signals, , Portability, Various
+@node Signals
@section Signals
@cindex signal handling
@cindex hangup
Other than that, Wget will not try to interfere with signals in any way.
@kbd{C-c}, @code{kill -TERM} and @code{kill -KILL} should kill it alike.
-@node Appendices, Copying, Various, Top
+@node Appendices
@chapter Appendices
This chapter contains some references I consider useful.
* Contributors:: People who helped.
@end menu
-@node Robot Exclusion, Security Considerations, Appendices, Appendices
+@node Robot Exclusion
@section Robot Exclusion
@cindex robot exclusion
@cindex robots.txt
reasonable rate (see the @samp{--wait} option), there's not much of a
problem. The trouble is that Wget can't tell the difference between the
smallest static page and the most demanding CGI. A site I know has a
-section handled by an, uh, @dfn{bitchin'} CGI Perl script that converts
-Info files to HTML on the fly. The script is slow, but works well
-enough for human users viewing an occasional Info file. However, when
-someone's recursive Wget download stumbles upon the index page that
-links to all the Info files through the script, the system is brought to
-its knees without providing anything useful to the downloader.
+section handled by a CGI Perl script that converts Info files to @sc{html} on
+the fly. The script is slow, but works well enough for human users
+viewing an occasional Info file. However, when someone's recursive Wget
+download stumbles upon the index page that links to all the Info files
+through the script, the system is brought to its knees without providing
+anything useful to the user (This task of converting Info files could be
+done locally and access to Info documentation for all installed GNU
+software on a system is available from the @code{info} command).
To avoid this kind of accident, as well as to preserve privacy for
documents that need to be protected from well-behaved robots, the
-concept of @dfn{robot exclusion} has been invented. The idea is that
+concept of @dfn{robot exclusion} was invented. The idea is that
the server administrators and document authors can specify which
-portions of the site they wish to protect from the robots.
-
-The most popular mechanism, and the de facto standard supported by all
-the major robots, is the ``Robots Exclusion Standard'' (RES) written by
-Martijn Koster et al. in 1994. It specifies the format of a text file
-containing directives that instruct the robots which URL paths to avoid.
-To be found by the robots, the specifications must be placed in
-@file{/robots.txt} in the server root, which the robots are supposed to
+portions of the site they wish to protect from robots and those
+they will permit access.
+
+The most popular mechanism, and the @i{de facto} standard supported by
+all the major robots, is the ``Robots Exclusion Standard'' (RES) written
+by Martijn Koster et al. in 1994. It specifies the format of a text
+file containing directives that instruct the robots which URL paths to
+avoid. To be found by the robots, the specifications must be placed in
+@file{/robots.txt} in the server root, which the robots are expected to
download and parse.
Although Wget is not a web robot in the strictest sense of the word, it
@file{.wgetrc}. You can achieve the same effect from the command line
using the @code{-e} switch, e.g. @samp{wget -e robots=off @var{url}...}.
-@node Security Considerations, Contributors, Robot Exclusion, Appendices
+@node Security Considerations
@section Security Considerations
@cindex security
me).
@end enumerate
-@node Contributors, , Security Considerations, Appendices
+@node Contributors
@section Contributors
@cindex contributors
@iftex
-GNU Wget was written by Hrvoje Nik@v{s}i@'{c} @email{hniksic@@arsdigita.com}.
+GNU Wget was written by Hrvoje Nik@v{s}i@'{c} @email{hniksic@@xemacs.org}.
@end iftex
-@ifinfo
-GNU Wget was written by Hrvoje Niksic @email{hniksic@@arsdigita.com}.
-@end ifinfo
+@ifnottex
+GNU Wget was written by Hrvoje Niksic @email{hniksic@@xemacs.org}.
+@end ifnottex
However, its development could never have gone as far as it has, were it
not for the help of many people, either with bug reports, feature
proposals, patches, or letters saying ``Thanks!''.
Zlatko @v{C}alu@v{s}i@'{c}, Tomislav Vujec and Dra@v{z}en
Ka@v{c}ar---feature suggestions and ``philosophical'' discussions.
@end iftex
-@ifinfo
+@ifnottex
Zlatko Calusic, Tomislav Vujec and Drazen Kacar---feature suggestions
and ``philosophical'' discussions.
-@end ifinfo
+@end ifnottex
@item
Darko Budor---initial port to Windows.
Tomislav Petrovi@'{c}, Mario Miko@v{c}evi@'{c}---many bug reports and
suggestions.
@end iftex
-@ifinfo
+@ifnottex
Tomislav Petrovic, Mario Mikocevic---many bug reports and suggestions.
-@end ifinfo
+@end ifnottex
@item
@iftex
Fran@,{c}ois Pinard---many thorough bug reports and discussions.
@end iftex
-@ifinfo
+@ifnottex
Francois Pinard---many thorough bug reports and discussions.
-@end ifinfo
+@end ifnottex
@item
Karl Eichwalder---lots of help with internationalization and other
@iftex
Kristijan @v{C}onka@v{s},
@end iftex
-@ifinfo
+@ifnottex
Kristijan Conkas,
-@end ifinfo
+@end ifnottex
John Daily,
+Ahmon Dancy,
Andrew Davison,
Andrew Deryabin,
Ulrich Drepper,
@iftex
Damir D@v{z}eko,
@end iftex
-@ifinfo
+@ifnottex
Damir Dzeko,
-@end ifinfo
+@end ifnottex
Alan Eldridge,
@iftex
Aleksandar Erkalovi@'{c},
@end iftex
-@ifinfo
+@ifnottex
Aleksandar Erkalovic,
-@end ifinfo
+@end ifnottex
Andy Eskilsson,
Christian Fraenkel,
Masashi Fujita,
Hans Grobler,
Mathieu Guillaume,
Dan Harkless,
+Aaron Hawley,
Herold Heiko,
Jochen Hein,
Karl Heuer,
@iftex
Mario Juri@'{c},
@end iftex
-@ifinfo
+@ifnottex
Mario Juric,
-@end ifinfo
+@end ifnottex
@iftex
Hack Kampbj@o rn,
@end iftex
-@ifinfo
+@ifnottex
Hack Kampbjorn,
-@end ifinfo
+@end ifnottex
Const Kaplinsky,
@iftex
Goran Kezunovi@'{c},
@end iftex
-@ifinfo
+@ifnottex
Goran Kezunovic,
-@end ifinfo
+@end ifnottex
Robert Kleine,
KOJIMA Haime,
Fila Kolodny,
\Xi\varepsilon\nu\iota\tau\acute{\epsilon}\lambda\lambda\eta\varsigma$
(Simos KSenitellis),
@end tex
-@ifinfo
+@ifnottex
Simos KSenitellis,
-@end ifinfo
+@end ifnottex
Hrvoje Lacko,
Daniel S. Lewart,
@iftex
Nicol@'{a}s Lichtmeier,
@end iftex
-@ifinfo
+@ifnottex
Nicolas Lichtmeier,
-@end ifinfo
+@end ifnottex
Dave Love,
Alexander V. Lukyanov,
+Thomas Lussnig,
+Aurelien Marchand,
Jordan Mendelson,
Lin Zhe Min,
Tim Mooney,
@iftex
Jan P@v{r}ikryl,
@end iftex
-@ifinfo
+@ifnottex
Jan Prikryl,
-@end ifinfo
+@end ifnottex
Marin Purgar,
@iftex
Csaba R@'{a}duly,
@end iftex
-@ifinfo
+@ifnottex
Csaba Raduly,
-@end ifinfo
+@end ifnottex
Keith Refson,
+Bill Richardson,
Tyler Riddle,
Tobias Ringstrom,
@c Texinfo doesn't grok @'{@i}, so we have to use TeX itself.
@tex
Juan Jos\'{e} Rodr\'{\i}gues,
@end tex
-@ifinfo
+@ifnottex
Juan Jose Rodrigues,
-@end ifinfo
+@end ifnottex
+Maciej W. Rozycki,
Edward J. Sabol,
Heinz Salzmann,
Robert Schmidt,
Szakacsits Szabolcs,
Mike Thomas,
Philipp Thomas,
+Mauro Tortonesi,
Dave Turner,
+Gisle Vanem,
Russell Vincent,
Charles G Waldman,
Douglas E. Wegscheid,
@iftex
Bojan @v{Z}drnja,
@end iftex
-@ifinfo
+@ifnottex
Bojan Zdrnja,
-@end ifinfo
+@end ifnottex
Kristijan Zimmer.
Apologies to all who I accidentally left out, and many thanks to all the
subscribers of the Wget mailing list.
-@node Copying, Concept Index, Appendices, Top
+@node Copying
@chapter Copying
@cindex copying
@cindex GPL
@cindex GFDL
@cindex free software
-GNU Wget is licensed under the GNU GPL, which makes it @dfn{free
-software}.
-
-Please note that ``free'' in ``free software'' refers to liberty, not
-price. As some GNU project advocates like to point out, think of ``free
-speech'' rather than ``free beer''. The exact and legally binding
-distribution terms are spelled out below; in short, you have the right
-(freedom) to run and change Wget and distribute it to other people, and
-even---if you want---charge money for doing either. The important
-restriction is that you have to grant your recipients the same rights
-and impose the same restrictions.
-
-This method of licensing software is also known as @dfn{open source}
-because, among other things, it makes sure that all recipients will
-receive the source code along with the program, and be able to improve
-it. The GNU project prefers the term ``free software'' for reasons
-outlined at
+GNU Wget is licensed under the GNU General Public License (GNU GPL),
+which makes it @dfn{free software}. Please note that ``free'' in ``free
+software'' refers to liberty, not price. As some people like to point
+out, it's the ``free'' of ``free speech'', not the ``free'' of ``free
+beer''.
+
+The exact and legally binding distribution terms are spelled out below.
+The GPL guarantees that you have the right (freedom) to run and change
+GNU Wget and distribute it to others, and even---if you want---charge
+money for doing any of those things. With these rights comes the
+obligation to distribute the source code along with the software and to
+grant your recipients the same rights and impose the same restrictions.
+
+This licensing model is also known as @dfn{open source} because it,
+among other things, makes sure that all recipients will receive the
+source code along with the program, and be able to improve it. The GNU
+project prefers the term ``free software'' for reasons outlined at
@url{http://www.gnu.org/philosophy/free-software-for-freedom.html}.
The exact license terms are defined by this paragraph and the GNU
@quotation
Permission is granted to copy, distribute and/or modify this document
-under the terms of the GNU Free Documentation License, Version 1.1 or
+under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with the
Invariant Sections being ``GNU General Public License'' and ``GNU Free
Documentation License'', with no Front-Cover Texts, and with no
* GNU Free Documentation License::
@end menu
-@node GNU General Public License, GNU Free Documentation License, Copying, Copying
+@node GNU General Public License
@section GNU General Public License
@center Version 2, June 1991
@iftex
@unnumberedsec TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
@end iftex
-@ifinfo
+@ifnottex
@center TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-@end ifinfo
+@end ifnottex
@enumerate
@item
@iftex
@heading NO WARRANTY
@end iftex
-@ifinfo
+@ifnottex
@center NO WARRANTY
-@end ifinfo
+@end ifnottex
@cindex no warranty
@item
@iftex
@heading END OF TERMS AND CONDITIONS
@end iftex
-@ifinfo
+@ifnottex
@center END OF TERMS AND CONDITIONS
-@end ifinfo
+@end ifnottex
@page
@unnumberedsec How to Apply These Terms to Your New Programs
library. If this is what you want to do, use the GNU Library General
Public License instead of this License.
-@node GNU Free Documentation License, , GNU General Public License, Copying
-@section GNU Free Documentation License
-@center Version 1.1, March 2000
-
-@display
-Copyright (C) 2000 Free Software Foundation, Inc.
-59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
-
-Everyone is permitted to copy and distribute verbatim copies
-of this license document, but changing it is not allowed.
-@end display
-@sp 1
-@enumerate 0
-@item
-PREAMBLE
-
-The purpose of this License is to make a manual, textbook, or other
-written document ``free'' in the sense of freedom: to assure everyone
-the effective freedom to copy and redistribute it, with or without
-modifying it, either commercially or noncommercially. Secondarily,
-this License preserves for the author and publisher a way to get
-credit for their work, while not being considered responsible for
-modifications made by others.
-
-This License is a kind of ``copyleft'', which means that derivative
-works of the document must themselves be free in the same sense. It
-complements the GNU General Public License, which is a copyleft
-license designed for free software.
-
-We have designed this License in order to use it for manuals for free
-software, because free software needs free documentation: a free
-program should come with manuals providing the same freedoms that the
-software does. But this License is not limited to software manuals;
-it can be used for any textual work, regardless of subject matter or
-whether it is published as a printed book. We recommend this License
-principally for works whose purpose is instruction or reference.
-
-@sp 1
-@item
-APPLICABILITY AND DEFINITIONS
-
-This License applies to any manual or other work that contains a
-notice placed by the copyright holder saying it can be distributed
-under the terms of this License. The ``Document'', below, refers to any
-such manual or work. Any member of the public is a licensee, and is
-addressed as ``you''.
-
-A ``Modified Version'' of the Document means any work containing the
-Document or a portion of it, either copied verbatim, or with
-modifications and/or translated into another language.
-
-A ``Secondary Section'' is a named appendix or a front-matter section of
-the Document that deals exclusively with the relationship of the
-publishers or authors of the Document to the Document's overall subject
-(or to related matters) and contains nothing that could fall directly
-within that overall subject. (For example, if the Document is in part a
-textbook of mathematics, a Secondary Section may not explain any
-mathematics.) The relationship could be a matter of historical
-connection with the subject or with related matters, or of legal,
-commercial, philosophical, ethical or political position regarding
-them.
-
-The ``Invariant Sections'' are certain Secondary Sections whose titles
-are designated, as being those of Invariant Sections, in the notice
-that says that the Document is released under this License.
-
-The ``Cover Texts'' are certain short passages of text that are listed,
-as Front-Cover Texts or Back-Cover Texts, in the notice that says that
-the Document is released under this License.
-
-A ``Transparent'' copy of the Document means a machine-readable copy,
-represented in a format whose specification is available to the
-general public, whose contents can be viewed and edited directly and
-straightforwardly with generic text editors or (for images composed of
-pixels) generic paint programs or (for drawings) some widely available
-drawing editor, and that is suitable for input to text formatters or
-for automatic translation to a variety of formats suitable for input
-to text formatters. A copy made in an otherwise Transparent file
-format whose markup has been designed to thwart or discourage
-subsequent modification by readers is not Transparent. A copy that is
-not ``Transparent'' is called ``Opaque''.
-
-Examples of suitable formats for Transparent copies include plain
-ASCII without markup, Texinfo input format, LaTeX input format, SGML
-or XML using a publicly available DTD, and standard-conforming simple
-HTML designed for human modification. Opaque formats include
-PostScript, PDF, proprietary formats that can be read and edited only
-by proprietary word processors, SGML or XML for which the DTD and/or
-processing tools are not generally available, and the
-machine-generated HTML produced by some word processors for output
-purposes only.
-
-The ``Title Page'' means, for a printed book, the title page itself,
-plus such following pages as are needed to hold, legibly, the material
-this License requires to appear in the title page. For works in
-formats which do not have any title page as such, ``Title Page'' means
-the text near the most prominent appearance of the work's title,
-preceding the beginning of the body of the text.
-@sp 1
-@item
-VERBATIM COPYING
-
-You may copy and distribute the Document in any medium, either
-commercially or noncommercially, provided that this License, the
-copyright notices, and the license notice saying this License applies
-to the Document are reproduced in all copies, and that you add no other
-conditions whatsoever to those of this License. You may not use
-technical measures to obstruct or control the reading or further
-copying of the copies you make or distribute. However, you may accept
-compensation in exchange for copies. If you distribute a large enough
-number of copies you must also follow the conditions in section 3.
-
-You may also lend copies, under the same conditions stated above, and
-you may publicly display copies.
-@sp 1
-@item
-COPYING IN QUANTITY
-
-If you publish printed copies of the Document numbering more than 100,
-and the Document's license notice requires Cover Texts, you must enclose
-the copies in covers that carry, clearly and legibly, all these Cover
-Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
-the back cover. Both covers must also clearly and legibly identify
-you as the publisher of these copies. The front cover must present
-the full title with all words of the title equally prominent and
-visible. You may add other material on the covers in addition.
-Copying with changes limited to the covers, as long as they preserve
-the title of the Document and satisfy these conditions, can be treated
-as verbatim copying in other respects.
-
-If the required texts for either cover are too voluminous to fit
-legibly, you should put the first ones listed (as many as fit
-reasonably) on the actual cover, and continue the rest onto adjacent
-pages.
-
-If you publish or distribute Opaque copies of the Document numbering
-more than 100, you must either include a machine-readable Transparent
-copy along with each Opaque copy, or state in or with each Opaque copy
-a publicly-accessible computer-network location containing a complete
-Transparent copy of the Document, free of added material, which the
-general network-using public has access to download anonymously at no
-charge using public-standard network protocols. If you use the latter
-option, you must take reasonably prudent steps, when you begin
-distribution of Opaque copies in quantity, to ensure that this
-Transparent copy will remain thus accessible at the stated location
-until at least one year after the last time you distribute an Opaque
-copy (directly or through your agents or retailers) of that edition to
-the public.
-
-It is requested, but not required, that you contact the authors of the
-Document well before redistributing any large number of copies, to give
-them a chance to provide you with an updated version of the Document.
-@sp 1
-@item
-MODIFICATIONS
-
-You may copy and distribute a Modified Version of the Document under
-the conditions of sections 2 and 3 above, provided that you release
-the Modified Version under precisely this License, with the Modified
-Version filling the role of the Document, thus licensing distribution
-and modification of the Modified Version to whoever possesses a copy
-of it. In addition, you must do these things in the Modified Version:
-
-A. Use in the Title Page (and on the covers, if any) a title distinct
- from that of the Document, and from those of previous versions
- (which should, if there were any, be listed in the History section
- of the Document). You may use the same title as a previous version
- if the original publisher of that version gives permission.@*
-B. List on the Title Page, as authors, one or more persons or entities
- responsible for authorship of the modifications in the Modified
- Version, together with at least five of the principal authors of the
- Document (all of its principal authors, if it has less than five).@*
-C. State on the Title page the name of the publisher of the
- Modified Version, as the publisher.@*
-D. Preserve all the copyright notices of the Document.@*
-E. Add an appropriate copyright notice for your modifications
- adjacent to the other copyright notices.@*
-F. Include, immediately after the copyright notices, a license notice
- giving the public permission to use the Modified Version under the
- terms of this License, in the form shown in the Addendum below.@*
-G. Preserve in that license notice the full lists of Invariant Sections
- and required Cover Texts given in the Document's license notice.@*
-H. Include an unaltered copy of this License.@*
-I. Preserve the section entitled ``History'', and its title, and add to
- it an item stating at least the title, year, new authors, and
- publisher of the Modified Version as given on the Title Page. If
- there is no section entitled ``History'' in the Document, create one
- stating the title, year, authors, and publisher of the Document as
- given on its Title Page, then add an item describing the Modified
- Version as stated in the previous sentence.@*
-J. Preserve the network location, if any, given in the Document for
- public access to a Transparent copy of the Document, and likewise
- the network locations given in the Document for previous versions
- it was based on. These may be placed in the ``History'' section.
- You may omit a network location for a work that was published at
- least four years before the Document itself, or if the original
- publisher of the version it refers to gives permission.@*
-K. In any section entitled ``Acknowledgements'' or ``Dedications'',
- preserve the section's title, and preserve in the section all the
- substance and tone of each of the contributor acknowledgements
- and/or dedications given therein.@*
-L. Preserve all the Invariant Sections of the Document,
- unaltered in their text and in their titles. Section numbers
- or the equivalent are not considered part of the section titles.@*
-M. Delete any section entitled ``Endorsements''. Such a section
- may not be included in the Modified Version.@*
-N. Do not retitle any existing section as ``Endorsements''
- or to conflict in title with any Invariant Section.@*
-@sp 1
-If the Modified Version includes new front-matter sections or
-appendices that qualify as Secondary Sections and contain no material
-copied from the Document, you may at your option designate some or all
-of these sections as invariant. To do this, add their titles to the
-list of Invariant Sections in the Modified Version's license notice.
-These titles must be distinct from any other section titles.
-
-You may add a section entitled ``Endorsements'', provided it contains
-nothing but endorsements of your Modified Version by various
-parties--for example, statements of peer review or that the text has
-been approved by an organization as the authoritative definition of a
-standard.
-
-You may add a passage of up to five words as a Front-Cover Text, and a
-passage of up to 25 words as a Back-Cover Text, to the end of the list
-of Cover Texts in the Modified Version. Only one passage of
-Front-Cover Text and one of Back-Cover Text may be added by (or
-through arrangements made by) any one entity. If the Document already
-includes a cover text for the same cover, previously added by you or
-by arrangement made by the same entity you are acting on behalf of,
-you may not add another; but you may replace the old one, on explicit
-permission from the previous publisher that added the old one.
-
-The author(s) and publisher(s) of the Document do not by this License
-give permission to use their names for publicity for or to assert or
-imply endorsement of any Modified Version.
-@sp 1
-@item
-COMBINING DOCUMENTS
-
-You may combine the Document with other documents released under this
-License, under the terms defined in section 4 above for modified
-versions, provided that you include in the combination all of the
-Invariant Sections of all of the original documents, unmodified, and
-list them all as Invariant Sections of your combined work in its
-license notice.
-
-The combined work need only contain one copy of this License, and
-multiple identical Invariant Sections may be replaced with a single
-copy. If there are multiple Invariant Sections with the same name but
-different contents, make the title of each such section unique by
-adding at the end of it, in parentheses, the name of the original
-author or publisher of that section if known, or else a unique number.
-Make the same adjustment to the section titles in the list of
-Invariant Sections in the license notice of the combined work.
-
-In the combination, you must combine any sections entitled ``History''
-in the various original documents, forming one section entitled
-``History''; likewise combine any sections entitled ``Acknowledgements'',
-and any sections entitled ``Dedications''. You must delete all sections
-entitled ``Endorsements.''
-@sp 1
-@item
-COLLECTIONS OF DOCUMENTS
-
-You may make a collection consisting of the Document and other documents
-released under this License, and replace the individual copies of this
-License in the various documents with a single copy that is included in
-the collection, provided that you follow the rules of this License for
-verbatim copying of each of the documents in all other respects.
-
-You may extract a single document from such a collection, and distribute
-it individually under this License, provided you insert a copy of this
-License into the extracted document, and follow this License in all
-other respects regarding verbatim copying of that document.
-@sp 1
-@item
-AGGREGATION WITH INDEPENDENT WORKS
-
-A compilation of the Document or its derivatives with other separate
-and independent documents or works, in or on a volume of a storage or
-distribution medium, does not as a whole count as a Modified Version
-of the Document, provided no compilation copyright is claimed for the
-compilation. Such a compilation is called an ``aggregate'', and this
-License does not apply to the other self-contained works thus compiled
-with the Document, on account of their being thus compiled, if they
-are not themselves derivative works of the Document.
-
-If the Cover Text requirement of section 3 is applicable to these
-copies of the Document, then if the Document is less than one quarter
-of the entire aggregate, the Document's Cover Texts may be placed on
-covers that surround only the Document within the aggregate.
-Otherwise they must appear on covers around the whole aggregate.
-@sp 1
-@item
-TRANSLATION
-
-Translation is considered a kind of modification, so you may
-distribute translations of the Document under the terms of section 4.
-Replacing Invariant Sections with translations requires special
-permission from their copyright holders, but you may include
-translations of some or all Invariant Sections in addition to the
-original versions of these Invariant Sections. You may include a
-translation of this License provided that you also include the
-original English version of this License. In case of a disagreement
-between the translation and the original English version of this
-License, the original English version will prevail.
-@sp 1
-@item
-TERMINATION
-
-You may not copy, modify, sublicense, or distribute the Document except
-as expressly provided for under this License. Any other attempt to
-copy, modify, sublicense or distribute the Document is void, and will
-automatically terminate your rights under this License. However,
-parties who have received copies, or rights, from you under this
-License will not have their licenses terminated so long as such
-parties remain in full compliance.
-@sp 1
-@item
-FUTURE REVISIONS OF THIS LICENSE
-
-The Free Software Foundation may publish new, revised versions
-of the GNU Free Documentation License from time to time. Such new
-versions will be similar in spirit to the present version, but may
-differ in detail to address new problems or concerns. See
-http://www.gnu.org/copyleft/.
-
-Each version of the License is given a distinguishing version number.
-If the Document specifies that a particular numbered version of this
-License ``or any later version'' applies to it, you have the option of
-following the terms and conditions either of that specified version or
-of any later version that has been published (not as a draft) by the
-Free Software Foundation. If the Document does not specify a version
-number of this License, you may choose any version ever published (not
-as a draft) by the Free Software Foundation.
-
-@end enumerate
-
-@unnumberedsec ADDENDUM: How to use this License for your documents
-
-To use this License in a document you have written, include a copy of
-the License in the document and put the following copyright and
-license notices just after the title page:
-
-@smallexample
-@group
-
- Copyright (C) @var{year} @var{your name}.
- Permission is granted to copy, distribute and/or modify this document
- under the terms of the GNU Free Documentation License, Version 1.1
- or any later version published by the Free Software Foundation;
- with the Invariant Sections being @var{list their titles}, with the
- Front-Cover Texts being @var{list}, and with the Back-Cover Texts being @var{list}.
- A copy of the license is included in the section entitled ``GNU
- Free Documentation License''.
-@end group
-@end smallexample
-If you have no Invariant Sections, write ``with no Invariant Sections''
-instead of saying which ones are invariant. If you have no
-Front-Cover Texts, write ``no Front-Cover Texts'' instead of
-``Front-Cover Texts being @var{list}''; likewise for Back-Cover Texts.
-
-If your document contains nontrivial examples of program code, we
-recommend releasing these examples in parallel under your choice of
-free software license, such as the GNU General Public License,
-to permit their use in free software.
-
+@include fdl.texi
-@node Concept Index, , Copying, Top
+@node Concept Index
@unnumbered Concept Index
@printindex cp