1 \input texinfo @c -*-texinfo-*-
6 @settitle GNU Wget @value{VERSION} Manual
7 @c Disable the monstrous rectangles beside overfull hbox-es.
9 @c Use `odd' to print double-sided.
14 @c Remove this if you don't use A4 paper.
18 @c Title for man page. The weird way texi2pod.pl is written requires
19 @c the preceding @set.
21 @c man title Wget The non-interactive network downloader.
23 @dircategory Network applications
25 * Wget: (wget). Non-interactive network downloader.
29 This file documents the GNU Wget utility for downloading network
32 @c man begin COPYRIGHT
33 Copyright @copyright{} 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003,
34 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011 Free Software Foundation,
38 Permission is granted to make and distribute verbatim copies of
39 this manual provided the copyright notice and this permission notice
40 are preserved on all copies.
44 Permission is granted to process this file through TeX and print the
45 results, provided the printed document carries a copying permission
46 notice identical to this one except for the removal of this paragraph
47 (this paragraph not being relevant to the printed manual).
49 Permission is granted to copy, distribute and/or modify this document
50 under the terms of the GNU Free Documentation License, Version 1.2 or
51 any later version published by the Free Software Foundation; with no
52 Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
53 copy of the license is included in the section entitled ``GNU Free
54 Documentation License''.
59 @title GNU Wget @value{VERSION}
60 @subtitle The non-interactive download utility
61 @subtitle Updated for Wget @value{VERSION}, @value{UPDATED}
62 @author by Hrvoje Nik@v{s}i@'{c} and others
66 Originally written by Hrvoje Niksic <hniksic@xemacs.org>.
69 This is @strong{not} the complete manual for GNU Wget.
70 For more complete information, including more detailed explanations of
71 some of the options, and a number of commands available
72 for use with @file{.wgetrc} files and the @samp{-e} option, see the GNU
73 Info entry for @file{wget}.
78 @vskip 0pt plus 1filll
85 @node Top, Overview, (dir), (dir)
86 @top Wget @value{VERSION}
92 * Overview:: Features of Wget.
93 * Invoking:: Wget command-line arguments.
94 * Recursive Download:: Downloading interlinked pages.
95 * Following Links:: The available methods of chasing links.
96 * Time-Stamping:: Mirroring according to time-stamps.
97 * Startup File:: Wget's initialization file.
98 * Examples:: Examples of usage.
99 * Various:: The stuff that doesn't fit anywhere else.
100 * Appendices:: Some useful references.
101 * Copying this manual:: You may give out copies of this manual.
102 * Concept Index:: Topics covered by this manual.
105 @node Overview, Invoking, Top, Top
110 @c man begin DESCRIPTION
111 GNU Wget is a free utility for non-interactive download of files from
112 the Web. It supports @sc{http}, @sc{https}, and @sc{ftp} protocols, as
113 well as retrieval through @sc{http} proxies.
116 This chapter is a partial overview of Wget's features.
120 @c man begin DESCRIPTION
121 Wget is non-interactive, meaning that it can work in the background,
122 while the user is not logged on. This allows you to start a retrieval
123 and disconnect from the system, letting Wget finish the work. By
124 contrast, most of the Web browsers require constant user's presence,
125 which can be a great hindrance when transferring a lot of data.
130 @c man begin DESCRIPTION
134 @c man begin DESCRIPTION
135 Wget can follow links in @sc{html}, @sc{xhtml}, and @sc{css} pages, to
136 create local versions of remote web sites, fully recreating the
137 directory structure of the original site. This is sometimes referred to
138 as ``recursive downloading.'' While doing that, Wget respects the Robot
139 Exclusion Standard (@file{/robots.txt}). Wget can be instructed to
140 convert the links in downloaded files to point at the local files, for
145 File name wildcard matching and recursive mirroring of directories are
146 available when retrieving via @sc{ftp}. Wget can read the time-stamp
147 information given by both @sc{http} and @sc{ftp} servers, and store it
148 locally. Thus Wget can see if the remote file has changed since last
149 retrieval, and automatically retrieve the new version if it has. This
150 makes Wget suitable for mirroring of @sc{ftp} sites, as well as home
155 @c man begin DESCRIPTION
159 @c man begin DESCRIPTION
160 Wget has been designed for robustness over slow or unstable network
161 connections; if a download fails due to a network problem, it will
162 keep retrying until the whole file has been retrieved. If the server
163 supports regetting, it will instruct the server to continue the
164 download from where it left off.
168 Wget supports proxy servers, which can lighten the network load, speed
169 up retrieval and provide access behind firewalls. Wget uses the passive
170 @sc{ftp} downloading by default, active @sc{ftp} being an option.
173 Wget supports IP version 6, the next generation of IP. IPv6 is
174 autodetected at compile-time, and can be disabled at either build or
175 run time. Binaries built with IPv6 support work well in both
176 IPv4-only and dual family environments.
179 Built-in features offer mechanisms to tune which links you wish to follow
180 (@pxref{Following Links}).
183 The progress of individual downloads is traced using a progress gauge.
184 Interactive downloads are tracked using a ``thermometer''-style gauge,
185 whereas non-interactive ones are traced with dots, each dot
186 representing a fixed amount of data received (1KB by default). Either
187 gauge can be customized to your preferences.
190 Most of the features are fully configurable, either through command line
191 options, or via the initialization file @file{.wgetrc} (@pxref{Startup
192 File}). Wget allows you to define @dfn{global} startup files
193 (@file{/usr/local/etc/wgetrc} by default) for site settings. You can also
194 specify the location of a startup file with the --config option.
200 @item /usr/local/etc/wgetrc
201 Default location of the @dfn{global} startup file.
210 Finally, GNU Wget is free software. This means that everyone may use
211 it, redistribute it and/or modify it under the terms of the GNU General
212 Public License, as published by the Free Software Foundation (see the
213 file @file{COPYING} that came with GNU Wget, for details).
216 @node Invoking, Recursive Download, Overview, Top
223 By default, Wget is very simple to invoke. The basic syntax is:
226 @c man begin SYNOPSIS
227 wget [@var{option}]@dots{} [@var{URL}]@dots{}
231 Wget will simply download all the @sc{url}s specified on the command
232 line. @var{URL} is a @dfn{Uniform Resource Locator}, as defined below.
234 However, you may wish to change some of the default parameters of
235 Wget. You can do it two ways: permanently, adding the appropriate
236 command to @file{.wgetrc} (@pxref{Startup File}), or specifying it on
242 * Basic Startup Options::
243 * Logging and Input File Options::
245 * Directory Options::
247 * HTTPS (SSL/TLS) Options::
249 * Recursive Retrieval Options::
250 * Recursive Accept/Reject Options::
254 @node URL Format, Option Syntax, Invoking, Invoking
259 @dfn{URL} is an acronym for Uniform Resource Locator. A uniform
260 resource locator is a compact string representation for a resource
261 available via the Internet. Wget recognizes the @sc{url} syntax as per
262 @sc{rfc1738}. This is the most widely used form (square brackets denote
266 http://host[:port]/directory/file
267 ftp://host[:port]/directory/file
270 You can also encode your username and password within a @sc{url}:
273 ftp://user:password@@host/path
274 http://user:password@@host/path
277 Either @var{user} or @var{password}, or both, may be left out. If you
278 leave out either the @sc{http} username or password, no authentication
279 will be sent. If you leave out the @sc{ftp} username, @samp{anonymous}
280 will be used. If you leave out the @sc{ftp} password, your email
281 address will be supplied as a default password.@footnote{If you have a
282 @file{.netrc} file in your home directory, password will also be
285 @strong{Important Note}: if you specify a password-containing @sc{url}
286 on the command line, the username and password will be plainly visible
287 to all users on the system, by way of @code{ps}. On multi-user systems,
288 this is a big security risk. To work around it, use @code{wget -i -}
289 and feed the @sc{url}s to Wget's standard input, each on a separate
290 line, terminated by @kbd{C-d}.
292 You can encode unsafe characters in a @sc{url} as @samp{%xy}, @code{xy}
293 being the hexadecimal representation of the character's @sc{ascii}
294 value. Some common unsafe characters include @samp{%} (quoted as
295 @samp{%25}), @samp{:} (quoted as @samp{%3A}), and @samp{@@} (quoted as
296 @samp{%40}). Refer to @sc{rfc1738} for a comprehensive list of unsafe
299 Wget also supports the @code{type} feature for @sc{ftp} @sc{url}s. By
300 default, @sc{ftp} documents are retrieved in the binary mode (type
301 @samp{i}), which means that they are downloaded unchanged. Another
302 useful mode is the @samp{a} (@dfn{ASCII}) mode, which converts the line
303 delimiters between the different operating systems, and is thus useful
304 for text files. Here is an example:
307 ftp://host/directory/file;type=a
310 Two alternative variants of @sc{url} specification are also supported,
311 because of historical (hysterical?) reasons and their widespreaded use.
313 @sc{ftp}-only syntax (supported by @code{NcFTP}):
318 @sc{http}-only syntax (introduced by @code{Netscape}):
323 These two alternative forms are deprecated, and may cease being
324 supported in the future.
326 If you do not understand the difference between these notations, or do
327 not know which one to use, just use the plain ordinary format you use
328 with your favorite browser, like @code{Lynx} or @code{Netscape}.
332 @node Option Syntax, Basic Startup Options, URL Format, Invoking
333 @section Option Syntax
334 @cindex option syntax
335 @cindex syntax of options
337 Since Wget uses GNU getopt to process command-line arguments, every
338 option has a long form along with the short one. Long options are
339 more convenient to remember, but take time to type. You may freely
340 mix different option styles, or specify options after the command-line
341 arguments. Thus you may write:
344 wget -r --tries=10 http://fly.srk.fer.hr/ -o log
347 The space between the option accepting an argument and the argument may
348 be omitted. Instead of @samp{-o log} you can write @samp{-olog}.
350 You may put several options that do not require arguments together,
357 This is completely equivalent to:
360 wget -d -r -c @var{URL}
363 Since the options can be specified after the arguments, you may
364 terminate them with @samp{--}. So the following will try to download
365 @sc{url} @samp{-x}, reporting failure to @file{log}:
371 The options that accept comma-separated lists all respect the convention
372 that specifying an empty list clears its value. This can be useful to
373 clear the @file{.wgetrc} settings. For instance, if your @file{.wgetrc}
374 sets @code{exclude_directories} to @file{/cgi-bin}, the following
375 example will first reset it, and then set it to exclude @file{/~nobody}
376 and @file{/~somebody}. You can also clear the lists in @file{.wgetrc}
377 (@pxref{Wgetrc Syntax}).
380 wget -X '' -X /~nobody,/~somebody
383 Most options that do not accept arguments are @dfn{boolean} options,
384 so named because their state can be captured with a yes-or-no
385 (``boolean'') variable. For example, @samp{--follow-ftp} tells Wget
386 to follow FTP links from HTML files and, on the other hand,
387 @samp{--no-glob} tells it not to perform file globbing on FTP URLs. A
388 boolean option is either @dfn{affirmative} or @dfn{negative}
389 (beginning with @samp{--no}). All such options share several
392 Unless stated otherwise, it is assumed that the default behavior is
393 the opposite of what the option accomplishes. For example, the
394 documented existence of @samp{--follow-ftp} assumes that the default
395 is to @emph{not} follow FTP links from HTML pages.
397 Affirmative options can be negated by prepending the @samp{--no-} to
398 the option name; negative options can be negated by omitting the
399 @samp{--no-} prefix. This might seem superfluous---if the default for
400 an affirmative option is to not do something, then why provide a way
401 to explicitly turn it off? But the startup file may in fact change
402 the default. For instance, using @code{follow_ftp = on} in
403 @file{.wgetrc} makes Wget @emph{follow} FTP links by default, and
404 using @samp{--no-follow-ftp} is the only way to restore the factory
405 default from the command line.
407 @node Basic Startup Options, Logging and Input File Options, Option Syntax, Invoking
408 @section Basic Startup Options
413 Display the version of Wget.
417 Print a help message describing all of Wget's command-line options.
421 Go to background immediately after startup. If no output file is
422 specified via the @samp{-o}, output is redirected to @file{wget-log}.
424 @cindex execute wgetrc command
425 @item -e @var{command}
426 @itemx --execute @var{command}
427 Execute @var{command} as if it were a part of @file{.wgetrc}
428 (@pxref{Startup File}). A command thus invoked will be executed
429 @emph{after} the commands in @file{.wgetrc}, thus taking precedence over
430 them. If you need to specify more than one wgetrc command, use multiple
431 instances of @samp{-e}.
435 @node Logging and Input File Options, Download Options, Basic Startup Options, Invoking
436 @section Logging and Input File Options
441 @item -o @var{logfile}
442 @itemx --output-file=@var{logfile}
443 Log all messages to @var{logfile}. The messages are normally reported
446 @cindex append to log
447 @item -a @var{logfile}
448 @itemx --append-output=@var{logfile}
449 Append to @var{logfile}. This is the same as @samp{-o}, only it appends
450 to @var{logfile} instead of overwriting the old log file. If
451 @var{logfile} does not exist, a new file is created.
456 Turn on debug output, meaning various information important to the
457 developers of Wget if it does not work properly. Your system
458 administrator may have chosen to compile Wget without debug support, in
459 which case @samp{-d} will not work. Please note that compiling with
460 debug support is always safe---Wget compiled with the debug support will
461 @emph{not} print any debug info unless requested with @samp{-d}.
462 @xref{Reporting Bugs}, for more information on how to use @samp{-d} for
468 Turn off Wget's output.
473 Turn on verbose output, with all the available data. The default output
478 Turn off verbose without being completely quiet (use @samp{-q} for
479 that), which means that error messages and basic information still get
483 @itemx --report-speed=@var{type}
484 Output bandwidth as @var{type}. The only accepted value is @samp{bits}.
488 @itemx --input-file=@var{file}
489 Read @sc{url}s from a local or external @var{file}. If @samp{-} is
490 specified as @var{file}, @sc{url}s are read from the standard input.
491 (Use @samp{./-} to read from a file literally named @samp{-}.)
493 If this function is used, no @sc{url}s need be present on the command
494 line. If there are @sc{url}s both on the command line and in an input
495 file, those on the command lines will be the first ones to be
496 retrieved. If @samp{--force-html} is not specified, then @var{file}
497 should consist of a series of URLs, one per line.
499 However, if you specify @samp{--force-html}, the document will be
500 regarded as @samp{html}. In that case you may have problems with
501 relative links, which you can solve either by adding @code{<base
502 href="@var{url}">} to the documents or by specifying
503 @samp{--base=@var{url}} on the command line.
505 If the @var{file} is an external one, the document will be automatically
506 treated as @samp{html} if the Content-Type matches @samp{text/html}.
507 Furthermore, the @var{file}'s location will be implicitly used as base
508 href if none was specified.
513 When input is read from a file, force it to be treated as an @sc{html}
514 file. This enables you to retrieve relative links from existing
515 @sc{html} files on your local disk, by adding @code{<base
516 href="@var{url}">} to @sc{html}, or using the @samp{--base} command-line
519 @cindex base for relative links in input file
521 @itemx --base=@var{URL}
522 Resolves relative links using @var{URL} as the point of reference,
523 when reading links from an HTML file specified via the
524 @samp{-i}/@samp{--input-file} option (together with
525 @samp{--force-html}, or when the input file was fetched remotely from
526 a server describing it as @sc{html}). This is equivalent to the
527 presence of a @code{BASE} tag in the @sc{html} input file, with
528 @var{URL} as the value for the @code{href} attribute.
530 For instance, if you specify @samp{http://foo/bar/a.html} for
531 @var{URL}, and Wget reads @samp{../baz/b.html} from the input file, it
532 would be resolved to @samp{http://foo/baz/b.html}.
534 @cindex specify config
535 @item --config=@var{FILE}
536 Specify the location of a startup file you wish to use.
539 @node Download Options, Directory Options, Logging and Input File Options, Invoking
540 @section Download Options
544 @cindex client IP address
545 @cindex IP address, client
546 @item --bind-address=@var{ADDRESS}
547 When making client TCP/IP connections, bind to @var{ADDRESS} on
548 the local machine. @var{ADDRESS} may be specified as a hostname or IP
549 address. This option can be useful if your machine is bound to multiple
554 @cindex number of retries
555 @item -t @var{number}
556 @itemx --tries=@var{number}
557 Set number of retries to @var{number}. Specify 0 or @samp{inf} for
558 infinite retrying. The default is to retry 20 times, with the exception
559 of fatal errors like ``connection refused'' or ``not found'' (404),
560 which are not retried.
563 @itemx --output-document=@var{file}
564 The documents will not be written to the appropriate files, but all
565 will be concatenated together and written to @var{file}. If @samp{-}
566 is used as @var{file}, documents will be printed to standard output,
567 disabling link conversion. (Use @samp{./-} to print to a file
568 literally named @samp{-}.)
570 Use of @samp{-O} is @emph{not} intended to mean simply ``use the name
571 @var{file} instead of the one in the URL;'' rather, it is
572 analogous to shell redirection:
573 @samp{wget -O file http://foo} is intended to work like
574 @samp{wget -O - http://foo > file}; @file{file} will be truncated
575 immediately, and @emph{all} downloaded content will be written there.
577 For this reason, @samp{-N} (for timestamp-checking) is not supported
578 in combination with @samp{-O}: since @var{file} is always newly
579 created, it will always have a very new timestamp. A warning will be
580 issued if this combination is used.
582 Similarly, using @samp{-r} or @samp{-p} with @samp{-O} may not work as
583 you expect: Wget won't just download the first file to @var{file} and
584 then download the rest to their normal names: @emph{all} downloaded
585 content will be placed in @var{file}. This was disabled in version
586 1.11, but has been reinstated (with a warning) in 1.11.2, as there are
587 some cases where this behavior can actually have some use.
589 Note that a combination with @samp{-k} is only permitted when
590 downloading a single document, as in that case it will just convert
591 all relative URIs to external ones; @samp{-k} makes no sense for
592 multiple URIs when they're all being downloaded to a single file;
593 @samp{-k} can be used only when the output is a regular file.
595 @cindex clobbering, file
596 @cindex downloading multiple times
600 If a file is downloaded more than once in the same directory, Wget's
601 behavior depends on a few options, including @samp{-nc}. In certain
602 cases, the local file will be @dfn{clobbered}, or overwritten, upon
603 repeated download. In other cases it will be preserved.
605 When running Wget without @samp{-N}, @samp{-nc}, @samp{-r}, or
606 @samp{-p}, downloading the same file in the same directory will result
607 in the original copy of @var{file} being preserved and the second copy
608 being named @samp{@var{file}.1}. If that file is downloaded yet
609 again, the third copy will be named @samp{@var{file}.2}, and so on.
610 (This is also the behavior with @samp{-nd}, even if @samp{-r} or
611 @samp{-p} are in effect.) When @samp{-nc} is specified, this behavior
612 is suppressed, and Wget will refuse to download newer copies of
613 @samp{@var{file}}. Therefore, ``@code{no-clobber}'' is actually a
614 misnomer in this mode---it's not clobbering that's prevented (as the
615 numeric suffixes were already preventing clobbering), but rather the
616 multiple version saving that's prevented.
618 When running Wget with @samp{-r} or @samp{-p}, but without @samp{-N},
619 @samp{-nd}, or @samp{-nc}, re-downloading a file will result in the
620 new copy simply overwriting the old. Adding @samp{-nc} will prevent
621 this behavior, instead causing the original version to be preserved
622 and any newer copies on the server to be ignored.
624 When running Wget with @samp{-N}, with or without @samp{-r} or
625 @samp{-p}, the decision as to whether or not to download a newer copy
626 of a file depends on the local and remote timestamp and size of the
627 file (@pxref{Time-Stamping}). @samp{-nc} may not be specified at the
628 same time as @samp{-N}.
630 Note that when @samp{-nc} is specified, files with the suffixes
631 @samp{.html} or @samp{.htm} will be loaded from the local disk and
632 parsed as if they had been retrieved from the Web.
634 @cindex continue retrieval
635 @cindex incomplete downloads
636 @cindex resume download
639 Continue getting a partially-downloaded file. This is useful when you
640 want to finish up a download started by a previous instance of Wget, or
641 by another program. For instance:
644 wget -c ftp://sunsite.doc.ic.ac.uk/ls-lR.Z
647 If there is a file named @file{ls-lR.Z} in the current directory, Wget
648 will assume that it is the first portion of the remote file, and will
649 ask the server to continue the retrieval from an offset equal to the
650 length of the local file.
652 Note that you don't need to specify this option if you just want the
653 current invocation of Wget to retry downloading a file should the
654 connection be lost midway through. This is the default behavior.
655 @samp{-c} only affects resumption of downloads started @emph{prior} to
656 this invocation of Wget, and whose local files are still sitting around.
658 Without @samp{-c}, the previous example would just download the remote
659 file to @file{ls-lR.Z.1}, leaving the truncated @file{ls-lR.Z} file
662 Beginning with Wget 1.7, if you use @samp{-c} on a non-empty file, and
663 it turns out that the server does not support continued downloading,
664 Wget will refuse to start the download from scratch, which would
665 effectively ruin existing contents. If you really want the download to
666 start from scratch, remove the file.
668 Also beginning with Wget 1.7, if you use @samp{-c} on a file which is of
669 equal size as the one on the server, Wget will refuse to download the
670 file and print an explanatory message. The same happens when the file
671 is smaller on the server than locally (presumably because it was changed
672 on the server since your last download attempt)---because ``continuing''
673 is not meaningful, no download occurs.
675 On the other side of the coin, while using @samp{-c}, any file that's
676 bigger on the server than locally will be considered an incomplete
677 download and only @code{(length(remote) - length(local))} bytes will be
678 downloaded and tacked onto the end of the local file. This behavior can
679 be desirable in certain cases---for instance, you can use @samp{wget -c}
680 to download just the new portion that's been appended to a data
681 collection or log file.
683 However, if the file is bigger on the server because it's been
684 @emph{changed}, as opposed to just @emph{appended} to, you'll end up
685 with a garbled file. Wget has no way of verifying that the local file
686 is really a valid prefix of the remote file. You need to be especially
687 careful of this when using @samp{-c} in conjunction with @samp{-r},
688 since every file will be considered as an "incomplete download" candidate.
690 Another instance where you'll get a garbled file if you try to use
691 @samp{-c} is if you have a lame @sc{http} proxy that inserts a
692 ``transfer interrupted'' string into the local file. In the future a
693 ``rollback'' option may be added to deal with this case.
695 Note that @samp{-c} only works with @sc{ftp} servers and with @sc{http}
696 servers that support the @code{Range} header.
698 @cindex progress indicator
700 @item --progress=@var{type}
701 Select the type of the progress indicator you wish to use. Legal
702 indicators are ``dot'' and ``bar''.
704 The ``bar'' indicator is used by default. It draws an @sc{ascii} progress
705 bar graphics (a.k.a ``thermometer'' display) indicating the status of
706 retrieval. If the output is not a TTY, the ``dot'' bar will be used by
709 Use @samp{--progress=dot} to switch to the ``dot'' display. It traces
710 the retrieval by printing dots on the screen, each dot representing a
711 fixed amount of downloaded data.
713 When using the dotted retrieval, you may also set the @dfn{style} by
714 specifying the type as @samp{dot:@var{style}}. Different styles assign
715 different meaning to one dot. With the @code{default} style each dot
716 represents 1K, there are ten dots in a cluster and 50 dots in a line.
717 The @code{binary} style has a more ``computer''-like orientation---8K
718 dots, 16-dots clusters and 48 dots per line (which makes for 384K
719 lines). The @code{mega} style is suitable for downloading very large
720 files---each dot represents 64K retrieved, there are eight dots in a
721 cluster, and 48 dots on each line (so each line contains 3M).
723 Note that you can set the default style using the @code{progress}
724 command in @file{.wgetrc}. That setting may be overridden from the
725 command line. The exception is that, when the output is not a TTY, the
726 ``dot'' progress will be favored over ``bar''. To force the bar output,
727 use @samp{--progress=bar:force}.
730 @itemx --timestamping
731 Turn on time-stamping. @xref{Time-Stamping}, for details.
733 @item --no-use-server-timestamps
734 Don't set the local file's timestamp by the one on the server.
736 By default, when a file is downloaded, it's timestamps are set to
737 match those from the remote file. This allows the use of
738 @samp{--timestamping} on subsequent invocations of wget. However, it
739 is sometimes useful to base the local file's timestamp on when it was
740 actually downloaded; for that purpose, the
741 @samp{--no-use-server-timestamps} option has been provided.
743 @cindex server response, print
745 @itemx --server-response
746 Print the headers sent by @sc{http} servers and responses sent by
749 @cindex Wget as spider
752 When invoked with this option, Wget will behave as a Web @dfn{spider},
753 which means that it will not download the pages, just check that they
754 are there. For example, you can use Wget to check your bookmarks:
757 wget --spider --force-html -i bookmarks.html
760 This feature needs much more work for Wget to get close to the
761 functionality of real web spiders.
765 @itemx --timeout=@var{seconds}
766 Set the network timeout to @var{seconds} seconds. This is equivalent
767 to specifying @samp{--dns-timeout}, @samp{--connect-timeout}, and
768 @samp{--read-timeout}, all at the same time.
770 When interacting with the network, Wget can check for timeout and
771 abort the operation if it takes too long. This prevents anomalies
772 like hanging reads and infinite connects. The only timeout enabled by
773 default is a 900-second read timeout. Setting a timeout to 0 disables
774 it altogether. Unless you know what you are doing, it is best not to
775 change the default timeout settings.
777 All timeout-related options accept decimal values, as well as
778 subsecond values. For example, @samp{0.1} seconds is a legal (though
779 unwise) choice of timeout. Subsecond timeouts are useful for checking
780 server response times or for testing network latency.
784 @item --dns-timeout=@var{seconds}
785 Set the DNS lookup timeout to @var{seconds} seconds. DNS lookups that
786 don't complete within the specified time will fail. By default, there
787 is no timeout on DNS lookups, other than that implemented by system
790 @cindex connect timeout
791 @cindex timeout, connect
792 @item --connect-timeout=@var{seconds}
793 Set the connect timeout to @var{seconds} seconds. TCP connections that
794 take longer to establish will be aborted. By default, there is no
795 connect timeout, other than that implemented by system libraries.
798 @cindex timeout, read
799 @item --read-timeout=@var{seconds}
800 Set the read (and write) timeout to @var{seconds} seconds. The
801 ``time'' of this timeout refers to @dfn{idle time}: if, at any point in
802 the download, no data is received for more than the specified number
803 of seconds, reading fails and the download is restarted. This option
804 does not directly affect the duration of the entire download.
806 Of course, the remote server may choose to terminate the connection
807 sooner than this option requires. The default read timeout is 900
810 @cindex bandwidth, limit
812 @cindex limit bandwidth
813 @item --limit-rate=@var{amount}
814 Limit the download speed to @var{amount} bytes per second. Amount may
815 be expressed in bytes, kilobytes with the @samp{k} suffix, or megabytes
816 with the @samp{m} suffix. For example, @samp{--limit-rate=20k} will
817 limit the retrieval rate to 20KB/s. This is useful when, for whatever
818 reason, you don't want Wget to consume the entire available bandwidth.
820 This option allows the use of decimal numbers, usually in conjunction
821 with power suffixes; for example, @samp{--limit-rate=2.5k} is a legal
824 Note that Wget implements the limiting by sleeping the appropriate
825 amount of time after a network read that took less time than specified
826 by the rate. Eventually this strategy causes the TCP transfer to slow
827 down to approximately the specified rate. However, it may take some
828 time for this balance to be achieved, so don't be surprised if limiting
829 the rate doesn't work well with very small files.
833 @item -w @var{seconds}
834 @itemx --wait=@var{seconds}
835 Wait the specified number of seconds between the retrievals. Use of
836 this option is recommended, as it lightens the server load by making the
837 requests less frequent. Instead of in seconds, the time can be
838 specified in minutes using the @code{m} suffix, in hours using @code{h}
839 suffix, or in days using @code{d} suffix.
841 Specifying a large value for this option is useful if the network or the
842 destination host is down, so that Wget can wait long enough to
843 reasonably expect the network error to be fixed before the retry. The
844 waiting interval specified by this function is influenced by
845 @code{--random-wait}, which see.
847 @cindex retries, waiting between
848 @cindex waiting between retries
849 @item --waitretry=@var{seconds}
850 If you don't want Wget to wait between @emph{every} retrieval, but only
851 between retries of failed downloads, you can use this option. Wget will
852 use @dfn{linear backoff}, waiting 1 second after the first failure on a
853 given file, then waiting 2 seconds after the second failure on that
854 file, up to the maximum number of @var{seconds} you specify.
856 By default, Wget will assume a value of 10 seconds.
861 Some web sites may perform log analysis to identify retrieval programs
862 such as Wget by looking for statistically significant similarities in
863 the time between requests. This option causes the time between requests
864 to vary between 0.5 and 1.5 * @var{wait} seconds, where @var{wait} was
865 specified using the @samp{--wait} option, in order to mask Wget's
866 presence from such analysis.
868 A 2001 article in a publication devoted to development on a popular
869 consumer platform provided code to perform this analysis on the fly.
870 Its author suggested blocking at the class C address level to ensure
871 automated retrieval programs were blocked despite changing DHCP-supplied
874 The @samp{--random-wait} option was inspired by this ill-advised
875 recommendation to block many unrelated users from a web site due to the
880 Don't use proxies, even if the appropriate @code{*_proxy} environment
884 For more information about the use of proxies with Wget, @xref{Proxies}.
889 @itemx --quota=@var{quota}
890 Specify download quota for automatic retrievals. The value can be
891 specified in bytes (default), kilobytes (with @samp{k} suffix), or
892 megabytes (with @samp{m} suffix).
894 Note that quota will never affect downloading a single file. So if you
895 specify @samp{wget -Q10k ftp://wuarchive.wustl.edu/ls-lR.gz}, all of the
896 @file{ls-lR.gz} will be downloaded. The same goes even when several
897 @sc{url}s are specified on the command-line. However, quota is
898 respected when retrieving either recursively, or from an input file.
899 Thus you may safely type @samp{wget -Q2m -i sites}---download will be
900 aborted when the quota is exceeded.
902 Setting quota to 0 or to @samp{inf} unlimits the download quota.
905 @cindex caching of DNS lookups
907 Turn off caching of DNS lookups. Normally, Wget remembers the IP
908 addresses it looked up from DNS so it doesn't have to repeatedly
909 contact the DNS server for the same (typically small) set of hosts it
910 retrieves from. This cache exists in memory only; a new Wget run will
913 However, it has been reported that in some situations it is not
914 desirable to cache host names, even for the duration of a
915 short-running application like Wget. With this option Wget issues a
916 new DNS lookup (more precisely, a new call to @code{gethostbyname} or
917 @code{getaddrinfo}) each time it makes a new connection. Please note
918 that this option will @emph{not} affect caching that might be
919 performed by the resolving library or by an external caching layer,
922 If you don't understand exactly what this option does, you probably
925 @cindex file names, restrict
926 @cindex Windows file names
927 @item --restrict-file-names=@var{modes}
928 Change which characters found in remote URLs must be escaped during
929 generation of local filenames. Characters that are @dfn{restricted}
930 by this option are escaped, i.e. replaced with @samp{%HH}, where
931 @samp{HH} is the hexadecimal number that corresponds to the restricted
932 character. This option may also be used to force all alphabetical
933 cases to be either lower- or uppercase.
935 By default, Wget escapes the characters that are not valid or safe as
936 part of file names on your operating system, as well as control
937 characters that are typically unprintable. This option is useful for
938 changing these defaults, perhaps because you are downloading to a
939 non-native partition, or because you want to disable escaping of the
940 control characters, or you want to further restrict characters to only
941 those in the @sc{ascii} range of values.
943 The @var{modes} are a comma-separated set of text values. The
944 acceptable values are @samp{unix}, @samp{windows}, @samp{nocontrol},
945 @samp{ascii}, @samp{lowercase}, and @samp{uppercase}. The values
946 @samp{unix} and @samp{windows} are mutually exclusive (one will
947 override the other), as are @samp{lowercase} and
948 @samp{uppercase}. Those last are special cases, as they do not change
949 the set of characters that would be escaped, but rather force local
950 file paths to be converted either to lower- or uppercase.
952 When ``unix'' is specified, Wget escapes the character @samp{/} and
953 the control characters in the ranges 0--31 and 128--159. This is the
954 default on Unix-like operating systems.
956 When ``windows'' is given, Wget escapes the characters @samp{\},
957 @samp{|}, @samp{/}, @samp{:}, @samp{?}, @samp{"}, @samp{*}, @samp{<},
958 @samp{>}, and the control characters in the ranges 0--31 and 128--159.
959 In addition to this, Wget in Windows mode uses @samp{+} instead of
960 @samp{:} to separate host and port in local file names, and uses
961 @samp{@@} instead of @samp{?} to separate the query portion of the file
962 name from the rest. Therefore, a URL that would be saved as
963 @samp{www.xemacs.org:4300/search.pl?input=blah} in Unix mode would be
964 saved as @samp{www.xemacs.org+4300/search.pl@@input=blah} in Windows
965 mode. This mode is the default on Windows.
967 If you specify @samp{nocontrol}, then the escaping of the control
968 characters is also switched off. This option may make sense
969 when you are downloading URLs whose names contain UTF-8 characters, on
970 a system which can save and display filenames in UTF-8 (some possible
971 byte values used in UTF-8 byte sequences fall in the range of values
972 designated by Wget as ``controls'').
974 The @samp{ascii} mode is used to specify that any bytes whose values
975 are outside the range of @sc{ascii} characters (that is, greater than
976 127) shall be escaped. This can be useful when saving filenames
977 whose encoding does not match the one used locally.
984 Force connecting to IPv4 or IPv6 addresses. With @samp{--inet4-only}
985 or @samp{-4}, Wget will only connect to IPv4 hosts, ignoring AAAA
986 records in DNS, and refusing to connect to IPv6 addresses specified in
987 URLs. Conversely, with @samp{--inet6-only} or @samp{-6}, Wget will
988 only connect to IPv6 hosts and ignore A records and IPv4 addresses.
990 Neither options should be needed normally. By default, an IPv6-aware
991 Wget will use the address family specified by the host's DNS record.
992 If the DNS responds with both IPv4 and IPv6 addresses, Wget will try
993 them in sequence until it finds one it can connect to. (Also see
994 @code{--prefer-family} option described below.)
996 These options can be used to deliberately force the use of IPv4 or
997 IPv6 address families on dual family systems, usually to aid debugging
998 or to deal with broken network configuration. Only one of
999 @samp{--inet6-only} and @samp{--inet4-only} may be specified at the
1000 same time. Neither option is available in Wget compiled without IPv6
1003 @item --prefer-family=none/IPv4/IPv6
1004 When given a choice of several addresses, connect to the addresses
1005 with specified address family first. The address order returned by
1006 DNS is used without change by default.
1008 This avoids spurious errors and connect attempts when accessing hosts
1009 that resolve to both IPv6 and IPv4 addresses from IPv4 networks. For
1010 example, @samp{www.kame.net} resolves to
1011 @samp{2001:200:0:8002:203:47ff:fea5:3085} and to
1012 @samp{203.178.141.194}. When the preferred family is @code{IPv4}, the
1013 IPv4 address is used first; when the preferred family is @code{IPv6},
1014 the IPv6 address is used first; if the specified value is @code{none},
1015 the address order returned by DNS is used without change.
1017 Unlike @samp{-4} and @samp{-6}, this option doesn't inhibit access to
1018 any address family, it only changes the @emph{order} in which the
1019 addresses are accessed. Also note that the reordering performed by
1020 this option is @dfn{stable}---it doesn't affect order of addresses of
1021 the same family. That is, the relative order of all IPv4 addresses
1022 and of all IPv6 addresses remains intact in all cases.
1024 @item --retry-connrefused
1025 Consider ``connection refused'' a transient error and try again.
1026 Normally Wget gives up on a URL when it is unable to connect to the
1027 site because failure to connect is taken as a sign that the server is
1028 not running at all and that retries would not help. This option is
1029 for mirroring unreliable sites whose servers tend to disappear for
1030 short periods of time.
1034 @cindex authentication
1035 @item --user=@var{user}
1036 @itemx --password=@var{password}
1037 Specify the username @var{user} and password @var{password} for both
1038 @sc{ftp} and @sc{http} file retrieval. These parameters can be overridden
1039 using the @samp{--ftp-user} and @samp{--ftp-password} options for
1040 @sc{ftp} connections and the @samp{--http-user} and @samp{--http-password}
1041 options for @sc{http} connections.
1043 @item --ask-password
1044 Prompt for a password for each connection established. Cannot be specified
1045 when @samp{--password} is being used, because they are mutually exclusive.
1051 Turn off internationalized URI (IRI) support. Use @samp{--iri} to
1052 turn it on. IRI support is activated by default.
1054 You can set the default state of IRI support using the @code{iri}
1055 command in @file{.wgetrc}. That setting may be overridden from the
1058 @cindex local encoding
1059 @item --local-encoding=@var{encoding}
1061 Force Wget to use @var{encoding} as the default system encoding. That affects
1062 how Wget converts URLs specified as arguments from locale to @sc{utf-8} for
1065 Wget use the function @code{nl_langinfo()} and then the @code{CHARSET}
1066 environment variable to get the locale. If it fails, @sc{ascii} is used.
1068 You can set the default local encoding using the @code{local_encoding}
1069 command in @file{.wgetrc}. That setting may be overridden from the
1072 @cindex remote encoding
1073 @item --remote-encoding=@var{encoding}
1075 Force Wget to use @var{encoding} as the default remote server encoding.
1076 That affects how Wget converts URIs found in files from remote encoding
1077 to @sc{utf-8} during a recursive fetch. This options is only useful for
1078 IRI support, for the interpretation of non-@sc{ascii} characters.
1080 For HTTP, remote encoding can be found in HTTP @code{Content-Type}
1081 header and in HTML @code{Content-Type http-equiv} meta tag.
1083 You can set the default encoding using the @code{remoteencoding}
1084 command in @file{.wgetrc}. That setting may be overridden from the
1090 Force Wget to unlink file instead of clobbering existing file. This
1091 option is useful for downloading to the directory with hardlinks.
1095 @node Directory Options, HTTP Options, Download Options, Invoking
1096 @section Directory Options
1100 @itemx --no-directories
1101 Do not create a hierarchy of directories when retrieving recursively.
1102 With this option turned on, all files will get saved to the current
1103 directory, without clobbering (if a name shows up more than once, the
1104 filenames will get extensions @samp{.n}).
1107 @itemx --force-directories
1108 The opposite of @samp{-nd}---create a hierarchy of directories, even if
1109 one would not have been created otherwise. E.g. @samp{wget -x
1110 http://fly.srk.fer.hr/robots.txt} will save the downloaded file to
1111 @file{fly.srk.fer.hr/robots.txt}.
1114 @itemx --no-host-directories
1115 Disable generation of host-prefixed directories. By default, invoking
1116 Wget with @samp{-r http://fly.srk.fer.hr/} will create a structure of
1117 directories beginning with @file{fly.srk.fer.hr/}. This option disables
1120 @item --protocol-directories
1121 Use the protocol name as a directory component of local file names. For
1122 example, with this option, @samp{wget -r http://@var{host}} will save to
1123 @samp{http/@var{host}/...} rather than just to @samp{@var{host}/...}.
1125 @cindex cut directories
1126 @item --cut-dirs=@var{number}
1127 Ignore @var{number} directory components. This is useful for getting a
1128 fine-grained control over the directory where recursive retrieval will
1131 Take, for example, the directory at
1132 @samp{ftp://ftp.xemacs.org/pub/xemacs/}. If you retrieve it with
1133 @samp{-r}, it will be saved locally under
1134 @file{ftp.xemacs.org/pub/xemacs/}. While the @samp{-nH} option can
1135 remove the @file{ftp.xemacs.org/} part, you are still stuck with
1136 @file{pub/xemacs}. This is where @samp{--cut-dirs} comes in handy; it
1137 makes Wget not ``see'' @var{number} remote directory components. Here
1138 are several examples of how @samp{--cut-dirs} option works.
1142 No options -> ftp.xemacs.org/pub/xemacs/
1144 -nH --cut-dirs=1 -> xemacs/
1145 -nH --cut-dirs=2 -> .
1147 --cut-dirs=1 -> ftp.xemacs.org/xemacs/
1152 If you just want to get rid of the directory structure, this option is
1153 similar to a combination of @samp{-nd} and @samp{-P}. However, unlike
1154 @samp{-nd}, @samp{--cut-dirs} does not lose with subdirectories---for
1155 instance, with @samp{-nH --cut-dirs=1}, a @file{beta/} subdirectory will
1156 be placed to @file{xemacs/beta}, as one would expect.
1158 @cindex directory prefix
1159 @item -P @var{prefix}
1160 @itemx --directory-prefix=@var{prefix}
1161 Set directory prefix to @var{prefix}. The @dfn{directory prefix} is the
1162 directory where all other files and subdirectories will be saved to,
1163 i.e. the top of the retrieval tree. The default is @samp{.} (the
1167 @node HTTP Options, HTTPS (SSL/TLS) Options, Directory Options, Invoking
1168 @section HTTP Options
1171 @cindex default page name
1173 @item --default-page=@var{name}
1174 Use @var{name} as the default file name when it isn't known (i.e., for
1175 URLs that end in a slash), instead of @file{index.html}.
1177 @cindex .html extension
1178 @cindex .css extension
1180 @itemx --adjust-extension
1181 If a file of type @samp{application/xhtml+xml} or @samp{text/html} is
1182 downloaded and the URL does not end with the regexp
1183 @samp{\.[Hh][Tt][Mm][Ll]?}, this option will cause the suffix @samp{.html}
1184 to be appended to the local filename. This is useful, for instance, when
1185 you're mirroring a remote site that uses @samp{.asp} pages, but you want
1186 the mirrored pages to be viewable on your stock Apache server. Another
1187 good use for this is when you're downloading CGI-generated materials. A URL
1188 like @samp{http://site.com/article.cgi?25} will be saved as
1189 @file{article.cgi?25.html}.
1191 Note that filenames changed in this way will be re-downloaded every time
1192 you re-mirror a site, because Wget can't tell that the local
1193 @file{@var{X}.html} file corresponds to remote URL @samp{@var{X}} (since
1194 it doesn't yet know that the URL produces output of type
1195 @samp{text/html} or @samp{application/xhtml+xml}.
1197 As of version 1.12, Wget will also ensure that any downloaded files of
1198 type @samp{text/css} end in the suffix @samp{.css}, and the option was
1199 renamed from @samp{--html-extension}, to better reflect its new
1200 behavior. The old option name is still acceptable, but should now be
1201 considered deprecated.
1203 At some point in the future, this option may well be expanded to
1204 include suffixes for other types of content, including content types
1205 that are not parsed by Wget.
1208 @cindex http password
1209 @cindex authentication
1210 @item --http-user=@var{user}
1211 @itemx --http-password=@var{password}
1212 Specify the username @var{user} and password @var{password} on an
1213 @sc{http} server. According to the type of the challenge, Wget will
1214 encode them using either the @code{basic} (insecure),
1215 the @code{digest}, or the Windows @code{NTLM} authentication scheme.
1217 Another way to specify username and password is in the @sc{url} itself
1218 (@pxref{URL Format}). Either method reveals your password to anyone who
1219 bothers to run @code{ps}. To prevent the passwords from being seen,
1220 store them in @file{.wgetrc} or @file{.netrc}, and make sure to protect
1221 those files from other users with @code{chmod}. If the passwords are
1222 really important, do not leave them lying in those files either---edit
1223 the files and delete them after Wget has started the download.
1226 For more information about security issues with Wget, @xref{Security
1230 @cindex Keep-Alive, turning off
1231 @cindex Persistent Connections, disabling
1232 @item --no-http-keep-alive
1233 Turn off the ``keep-alive'' feature for HTTP downloads. Normally, Wget
1234 asks the server to keep the connection open so that, when you download
1235 more than one document from the same server, they get transferred over
1236 the same TCP connection. This saves time and at the same time reduces
1237 the load on the server.
1239 This option is useful when, for some reason, persistent (keep-alive)
1240 connections don't work for you, for example due to a server bug or due
1241 to the inability of server-side scripts to cope with the connections.
1246 Disable server-side cache. In this case, Wget will send the remote
1247 server an appropriate directive (@samp{Pragma: no-cache}) to get the
1248 file from the remote service, rather than returning the cached version.
1249 This is especially useful for retrieving and flushing out-of-date
1250 documents on proxy servers.
1252 Caching is allowed by default.
1256 Disable the use of cookies. Cookies are a mechanism for maintaining
1257 server-side state. The server sends the client a cookie using the
1258 @code{Set-Cookie} header, and the client responds with the same cookie
1259 upon further requests. Since cookies allow the server owners to keep
1260 track of visitors and for sites to exchange this information, some
1261 consider them a breach of privacy. The default is to use cookies;
1262 however, @emph{storing} cookies is not on by default.
1264 @cindex loading cookies
1265 @cindex cookies, loading
1266 @item --load-cookies @var{file}
1267 Load cookies from @var{file} before the first HTTP retrieval.
1268 @var{file} is a textual file in the format originally used by Netscape's
1269 @file{cookies.txt} file.
1271 You will typically use this option when mirroring sites that require
1272 that you be logged in to access some or all of their content. The login
1273 process typically works by the web server issuing an @sc{http} cookie
1274 upon receiving and verifying your credentials. The cookie is then
1275 resent by the browser when accessing that part of the site, and so
1276 proves your identity.
1278 Mirroring such a site requires Wget to send the same cookies your
1279 browser sends when communicating with the site. This is achieved by
1280 @samp{--load-cookies}---simply point Wget to the location of the
1281 @file{cookies.txt} file, and it will send the same cookies your browser
1282 would send in the same situation. Different browsers keep textual
1283 cookie files in different locations:
1287 The cookies are in @file{~/.netscape/cookies.txt}.
1289 @item Mozilla and Netscape 6.x.
1290 Mozilla's cookie file is also named @file{cookies.txt}, located
1291 somewhere under @file{~/.mozilla}, in the directory of your profile.
1292 The full path usually ends up looking somewhat like
1293 @file{~/.mozilla/default/@var{some-weird-string}/cookies.txt}.
1295 @item Internet Explorer.
1296 You can produce a cookie file Wget can use by using the File menu,
1297 Import and Export, Export Cookies. This has been tested with Internet
1298 Explorer 5; it is not guaranteed to work with earlier versions.
1300 @item Other browsers.
1301 If you are using a different browser to create your cookies,
1302 @samp{--load-cookies} will only work if you can locate or produce a
1303 cookie file in the Netscape format that Wget expects.
1306 If you cannot use @samp{--load-cookies}, there might still be an
1307 alternative. If your browser supports a ``cookie manager'', you can use
1308 it to view the cookies used when accessing the site you're mirroring.
1309 Write down the name and value of the cookie, and manually instruct Wget
1310 to send those cookies, bypassing the ``official'' cookie support:
1313 wget --no-cookies --header "Cookie: @var{name}=@var{value}"
1316 @cindex saving cookies
1317 @cindex cookies, saving
1318 @item --save-cookies @var{file}
1319 Save cookies to @var{file} before exiting. This will not save cookies
1320 that have expired or that have no expiry time (so-called ``session
1321 cookies''), but also see @samp{--keep-session-cookies}.
1323 @cindex cookies, session
1324 @cindex session cookies
1325 @item --keep-session-cookies
1326 When specified, causes @samp{--save-cookies} to also save session
1327 cookies. Session cookies are normally not saved because they are
1328 meant to be kept in memory and forgotten when you exit the browser.
1329 Saving them is useful on sites that require you to log in or to visit
1330 the home page before you can access some pages. With this option,
1331 multiple Wget runs are considered a single browser session as far as
1332 the site is concerned.
1334 Since the cookie file format does not normally carry session cookies,
1335 Wget marks them with an expiry timestamp of 0. Wget's
1336 @samp{--load-cookies} recognizes those as session cookies, but it might
1337 confuse other browsers. Also note that cookies so loaded will be
1338 treated as other session cookies, which means that if you want
1339 @samp{--save-cookies} to preserve them again, you must use
1340 @samp{--keep-session-cookies} again.
1342 @cindex Content-Length, ignore
1343 @cindex ignore length
1344 @item --ignore-length
1345 Unfortunately, some @sc{http} servers (@sc{cgi} programs, to be more
1346 precise) send out bogus @code{Content-Length} headers, which makes Wget
1347 go wild, as it thinks not all the document was retrieved. You can spot
1348 this syndrome if Wget retries getting the same document again and again,
1349 each time claiming that the (otherwise normal) connection has closed on
1352 With this option, Wget will ignore the @code{Content-Length} header---as
1353 if it never existed.
1356 @item --header=@var{header-line}
1357 Send @var{header-line} along with the rest of the headers in each
1358 @sc{http} request. The supplied header is sent as-is, which means it
1359 must contain name and value separated by colon, and must not contain
1362 You may define more than one additional header by specifying
1363 @samp{--header} more than once.
1367 wget --header='Accept-Charset: iso-8859-2' \
1368 --header='Accept-Language: hr' \
1369 http://fly.srk.fer.hr/
1373 Specification of an empty string as the header value will clear all
1374 previous user-defined headers.
1376 As of Wget 1.10, this option can be used to override headers otherwise
1377 generated automatically. This example instructs Wget to connect to
1378 localhost, but to specify @samp{foo.bar} in the @code{Host} header:
1381 wget --header="Host: foo.bar" http://localhost/
1384 In versions of Wget prior to 1.10 such use of @samp{--header} caused
1385 sending of duplicate headers.
1388 @item --max-redirect=@var{number}
1389 Specifies the maximum number of redirections to follow for a resource.
1390 The default is 20, which is usually far more than necessary. However, on
1391 those occasions where you want to allow more (or fewer), this is the
1395 @cindex proxy password
1396 @cindex proxy authentication
1397 @item --proxy-user=@var{user}
1398 @itemx --proxy-password=@var{password}
1399 Specify the username @var{user} and password @var{password} for
1400 authentication on a proxy server. Wget will encode them using the
1401 @code{basic} authentication scheme.
1403 Security considerations similar to those with @samp{--http-password}
1404 pertain here as well.
1406 @cindex http referer
1407 @cindex referer, http
1408 @item --referer=@var{url}
1409 Include `Referer: @var{url}' header in HTTP request. Useful for
1410 retrieving documents with server-side processing that assume they are
1411 always being retrieved by interactive web browsers and only come out
1412 properly when Referer is set to one of the pages that point to them.
1414 @cindex server response, save
1415 @item --save-headers
1416 Save the headers sent by the @sc{http} server to the file, preceding the
1417 actual contents, with an empty line as the separator.
1420 @item -U @var{agent-string}
1421 @itemx --user-agent=@var{agent-string}
1422 Identify as @var{agent-string} to the @sc{http} server.
1424 The @sc{http} protocol allows the clients to identify themselves using a
1425 @code{User-Agent} header field. This enables distinguishing the
1426 @sc{www} software, usually for statistical purposes or for tracing of
1427 protocol violations. Wget normally identifies as
1428 @samp{Wget/@var{version}}, @var{version} being the current version
1431 However, some sites have been known to impose the policy of tailoring
1432 the output according to the @code{User-Agent}-supplied information.
1433 While this is not such a bad idea in theory, it has been abused by
1434 servers denying information to clients other than (historically)
1435 Netscape or, more frequently, Microsoft Internet Explorer. This
1436 option allows you to change the @code{User-Agent} line issued by Wget.
1437 Use of this option is discouraged, unless you really know what you are
1440 Specifying empty user agent with @samp{--user-agent=""} instructs Wget
1441 not to send the @code{User-Agent} header in @sc{http} requests.
1444 @item --post-data=@var{string}
1445 @itemx --post-file=@var{file}
1446 Use POST as the method for all HTTP requests and send the specified
1447 data in the request body. @samp{--post-data} sends @var{string} as
1448 data, whereas @samp{--post-file} sends the contents of @var{file}.
1449 Other than that, they work in exactly the same way. In particular,
1450 they @emph{both} expect content of the form @code{key1=value1&key2=value2},
1451 with percent-encoding for special characters; the only difference is
1452 that one expects its content as a command-line parameter and the other
1453 accepts its content from a file. In particular, @samp{--post-file} is
1454 @emph{not} for transmitting files as form attachments: those must
1455 appear as @code{key=value} data (with appropriate percent-coding) just
1456 like everything else. Wget does not currently support
1457 @code{multipart/form-data} for transmitting POST data; only
1458 @code{application/x-www-form-urlencoded}. Only one of
1459 @samp{--post-data} and @samp{--post-file} should be specified.
1461 Please be aware that Wget needs to know the size of the POST data in
1462 advance. Therefore the argument to @code{--post-file} must be a regular
1463 file; specifying a FIFO or something like @file{/dev/stdin} won't work.
1464 It's not quite clear how to work around this limitation inherent in
1465 HTTP/1.0. Although HTTP/1.1 introduces @dfn{chunked} transfer that
1466 doesn't require knowing the request length in advance, a client can't
1467 use chunked unless it knows it's talking to an HTTP/1.1 server. And it
1468 can't know that until it receives a response, which in turn requires the
1469 request to have been completed -- a chicken-and-egg problem.
1471 Note: if Wget is redirected after the POST request is completed, it
1472 will not send the POST data to the redirected URL. This is because
1473 URLs that process POST often respond with a redirection to a regular
1474 page, which does not desire or accept POST. It is not completely
1475 clear that this behavior is optimal; if it doesn't work out, it might
1476 be changed in the future.
1478 This example shows how to log to a server using POST and then proceed to
1479 download the desired pages, presumably only accessible to authorized
1484 # @r{Log in to the server. This can be done only once.}
1485 wget --save-cookies cookies.txt \
1486 --post-data 'user=foo&password=bar' \
1487 http://server.com/auth.php
1489 # @r{Now grab the page or pages we care about.}
1490 wget --load-cookies cookies.txt \
1491 -p http://server.com/interesting/article.php
1495 If the server is using session cookies to track user authentication,
1496 the above will not work because @samp{--save-cookies} will not save
1497 them (and neither will browsers) and the @file{cookies.txt} file will
1498 be empty. In that case use @samp{--keep-session-cookies} along with
1499 @samp{--save-cookies} to force saving of session cookies.
1501 @cindex Content-Disposition
1502 @item --content-disposition
1504 If this is set to on, experimental (not fully-functional) support for
1505 @code{Content-Disposition} headers is enabled. This can currently result in
1506 extra round-trips to the server for a @code{HEAD} request, and is known
1507 to suffer from a few bugs, which is why it is not currently enabled by default.
1509 This option is useful for some file-downloading CGI programs that use
1510 @code{Content-Disposition} headers to describe what the name of a
1511 downloaded file should be.
1513 @cindex Content On Error
1514 @item --content-on-error
1516 If this is set to on, wget will not skip the content when the server responds
1517 with a http status code that indicates error.
1519 @cindex Trust server names
1520 @item --trust-server-names
1522 If this is set to on, on a redirect the last component of the
1523 redirection URL will be used as the local file name. By default it is
1524 used the last component in the original URL.
1526 @cindex authentication
1527 @item --auth-no-challenge
1529 If this option is given, Wget will send Basic HTTP authentication
1530 information (plaintext username and password) for all requests, just
1531 like Wget 1.10.2 and prior did by default.
1533 Use of this option is not recommended, and is intended only to support
1534 some few obscure servers, which never send HTTP authentication
1535 challenges, but accept unsolicited auth info, say, in addition to
1536 form-based authentication.
1540 @node HTTPS (SSL/TLS) Options, FTP Options, HTTP Options, Invoking
1541 @section HTTPS (SSL/TLS) Options
1544 To support encrypted HTTP (HTTPS) downloads, Wget must be compiled
1545 with an external SSL library, currently OpenSSL. If Wget is compiled
1546 without SSL support, none of these options are available.
1549 @cindex SSL protocol, choose
1550 @item --secure-protocol=@var{protocol}
1551 Choose the secure protocol to be used. Legal values are @samp{auto},
1552 @samp{SSLv2}, @samp{SSLv3}, and @samp{TLSv1}. If @samp{auto} is used,
1553 the SSL library is given the liberty of choosing the appropriate
1554 protocol automatically, which is achieved by sending an SSLv2 greeting
1555 and announcing support for SSLv3 and TLSv1. This is the default.
1557 Specifying @samp{SSLv2}, @samp{SSLv3}, or @samp{TLSv1} forces the use
1558 of the corresponding protocol. This is useful when talking to old and
1559 buggy SSL server implementations that make it hard for OpenSSL to
1560 choose the correct protocol version. Fortunately, such servers are
1563 @cindex SSL certificate, check
1564 @item --no-check-certificate
1565 Don't check the server certificate against the available certificate
1566 authorities. Also don't require the URL host name to match the common
1567 name presented by the certificate.
1569 As of Wget 1.10, the default is to verify the server's certificate
1570 against the recognized certificate authorities, breaking the SSL
1571 handshake and aborting the download if the verification fails.
1572 Although this provides more secure downloads, it does break
1573 interoperability with some sites that worked with previous Wget
1574 versions, particularly those using self-signed, expired, or otherwise
1575 invalid certificates. This option forces an ``insecure'' mode of
1576 operation that turns the certificate verification errors into warnings
1577 and allows you to proceed.
1579 If you encounter ``certificate verification'' errors or ones saying
1580 that ``common name doesn't match requested host name'', you can use
1581 this option to bypass the verification and proceed with the download.
1582 @emph{Only use this option if you are otherwise convinced of the
1583 site's authenticity, or if you really don't care about the validity of
1584 its certificate.} It is almost always a bad idea not to check the
1585 certificates when transmitting confidential or important data.
1587 @cindex SSL certificate
1588 @item --certificate=@var{file}
1589 Use the client certificate stored in @var{file}. This is needed for
1590 servers that are configured to require certificates from the clients
1591 that connect to them. Normally a certificate is not required and this
1594 @cindex SSL certificate type, specify
1595 @item --certificate-type=@var{type}
1596 Specify the type of the client certificate. Legal values are
1597 @samp{PEM} (assumed by default) and @samp{DER}, also known as
1600 @item --private-key=@var{file}
1601 Read the private key from @var{file}. This allows you to provide the
1602 private key in a file separate from the certificate.
1604 @item --private-key-type=@var{type}
1605 Specify the type of the private key. Accepted values are @samp{PEM}
1606 (the default) and @samp{DER}.
1608 @item --ca-certificate=@var{file}
1609 Use @var{file} as the file with the bundle of certificate authorities
1610 (``CA'') to verify the peers. The certificates must be in PEM format.
1612 Without this option Wget looks for CA certificates at the
1613 system-specified locations, chosen at OpenSSL installation time.
1615 @cindex SSL certificate authority
1616 @item --ca-directory=@var{directory}
1617 Specifies directory containing CA certificates in PEM format. Each
1618 file contains one CA certificate, and the file name is based on a hash
1619 value derived from the certificate. This is achieved by processing a
1620 certificate directory with the @code{c_rehash} utility supplied with
1621 OpenSSL. Using @samp{--ca-directory} is more efficient than
1622 @samp{--ca-certificate} when many certificates are installed because
1623 it allows Wget to fetch certificates on demand.
1625 Without this option Wget looks for CA certificates at the
1626 system-specified locations, chosen at OpenSSL installation time.
1628 @cindex entropy, specifying source of
1629 @cindex randomness, specifying source of
1630 @item --random-file=@var{file}
1631 Use @var{file} as the source of random data for seeding the
1632 pseudo-random number generator on systems without @file{/dev/random}.
1634 On such systems the SSL library needs an external source of randomness
1635 to initialize. Randomness may be provided by EGD (see
1636 @samp{--egd-file} below) or read from an external source specified by
1637 the user. If this option is not specified, Wget looks for random data
1638 in @code{$RANDFILE} or, if that is unset, in @file{$HOME/.rnd}. If
1639 none of those are available, it is likely that SSL encryption will not
1642 If you're getting the ``Could not seed OpenSSL PRNG; disabling SSL.''
1643 error, you should provide random data using some of the methods
1647 @item --egd-file=@var{file}
1648 Use @var{file} as the EGD socket. EGD stands for @dfn{Entropy
1649 Gathering Daemon}, a user-space program that collects data from
1650 various unpredictable system sources and makes it available to other
1651 programs that might need it. Encryption software, such as the SSL
1652 library, needs sources of non-repeating randomness to seed the random
1653 number generator used to produce cryptographically strong keys.
1655 OpenSSL allows the user to specify his own source of entropy using the
1656 @code{RAND_FILE} environment variable. If this variable is unset, or
1657 if the specified file does not produce enough randomness, OpenSSL will
1658 read random data from EGD socket specified using this option.
1660 If this option is not specified (and the equivalent startup command is
1661 not used), EGD is never contacted. EGD is not needed on modern Unix
1662 systems that support @file{/dev/random}.
1667 @item --warc-file=@var{file}
1668 Use @var{file} as the destination WARC file.
1670 @item --warc-header=@var{string}
1671 Use @var{string} into as the warcinfo record.
1673 @item --warc-max-size=@var{size}
1674 Set the maximum size of the WARC files to @var{size}.
1677 Write CDX index files.
1679 @item --warc-dedup=@var{file}
1680 Do not store records listed in this CDX file.
1682 @item --no-warc-compression
1683 Do not compress WARC files with GZIP.
1685 @item --no-warc-digests
1686 Do not calculate SHA1 digests.
1688 @item --no-warc-keep-log
1689 Do not store the log file in a WARC record.
1691 @item --warc-tempdir=@var{dir}
1692 Specify the location for temporary files created by the WARC writer.
1695 @node FTP Options, Recursive Retrieval Options, HTTPS (SSL/TLS) Options, Invoking
1696 @section FTP Options
1700 @cindex ftp password
1701 @cindex ftp authentication
1702 @item --ftp-user=@var{user}
1703 @itemx --ftp-password=@var{password}
1704 Specify the username @var{user} and password @var{password} on an
1705 @sc{ftp} server. Without this, or the corresponding startup option,
1706 the password defaults to @samp{-wget@@}, normally used for anonymous
1709 Another way to specify username and password is in the @sc{url} itself
1710 (@pxref{URL Format}). Either method reveals your password to anyone who
1711 bothers to run @code{ps}. To prevent the passwords from being seen,
1712 store them in @file{.wgetrc} or @file{.netrc}, and make sure to protect
1713 those files from other users with @code{chmod}. If the passwords are
1714 really important, do not leave them lying in those files either---edit
1715 the files and delete them after Wget has started the download.
1718 For more information about security issues with Wget, @xref{Security
1722 @cindex .listing files, removing
1723 @item --no-remove-listing
1724 Don't remove the temporary @file{.listing} files generated by @sc{ftp}
1725 retrievals. Normally, these files contain the raw directory listings
1726 received from @sc{ftp} servers. Not removing them can be useful for
1727 debugging purposes, or when you want to be able to easily check on the
1728 contents of remote server directories (e.g. to verify that a mirror
1729 you're running is complete).
1731 Note that even though Wget writes to a known filename for this file,
1732 this is not a security hole in the scenario of a user making
1733 @file{.listing} a symbolic link to @file{/etc/passwd} or something and
1734 asking @code{root} to run Wget in his or her directory. Depending on
1735 the options used, either Wget will refuse to write to @file{.listing},
1736 making the globbing/recursion/time-stamping operation fail, or the
1737 symbolic link will be deleted and replaced with the actual
1738 @file{.listing} file, or the listing will be written to a
1739 @file{.listing.@var{number}} file.
1741 Even though this situation isn't a problem, though, @code{root} should
1742 never run Wget in a non-trusted user's directory. A user could do
1743 something as simple as linking @file{index.html} to @file{/etc/passwd}
1744 and asking @code{root} to run Wget with @samp{-N} or @samp{-r} so the file
1745 will be overwritten.
1747 @cindex globbing, toggle
1749 Turn off @sc{ftp} globbing. Globbing refers to the use of shell-like
1750 special characters (@dfn{wildcards}), like @samp{*}, @samp{?}, @samp{[}
1751 and @samp{]} to retrieve more than one file from the same directory at
1755 wget ftp://gnjilux.srk.fer.hr/*.msg
1758 By default, globbing will be turned on if the @sc{url} contains a
1759 globbing character. This option may be used to turn globbing on or off
1762 You may have to quote the @sc{url} to protect it from being expanded by
1763 your shell. Globbing makes Wget look for a directory listing, which is
1764 system-specific. This is why it currently works only with Unix @sc{ftp}
1765 servers (and the ones emulating Unix @code{ls} output).
1768 @item --no-passive-ftp
1769 Disable the use of the @dfn{passive} FTP transfer mode. Passive FTP
1770 mandates that the client connect to the server to establish the data
1771 connection rather than the other way around.
1773 If the machine is connected to the Internet directly, both passive and
1774 active FTP should work equally well. Behind most firewall and NAT
1775 configurations passive FTP has a better chance of working. However,
1776 in some rare firewall configurations, active FTP actually works when
1777 passive FTP doesn't. If you suspect this to be the case, use this
1778 option, or set @code{passive_ftp=off} in your init file.
1780 @cindex symbolic links, retrieving
1781 @item --retr-symlinks
1782 Usually, when retrieving @sc{ftp} directories recursively and a symbolic
1783 link is encountered, the linked-to file is not downloaded. Instead, a
1784 matching symbolic link is created on the local filesystem. The
1785 pointed-to file will not be downloaded unless this recursive retrieval
1786 would have encountered it separately and downloaded it anyway.
1788 When @samp{--retr-symlinks} is specified, however, symbolic links are
1789 traversed and the pointed-to files are retrieved. At this time, this
1790 option does not cause Wget to traverse symlinks to directories and
1791 recurse through them, but in the future it should be enhanced to do
1794 Note that when retrieving a file (not a directory) because it was
1795 specified on the command-line, rather than because it was recursed to,
1796 this option has no effect. Symbolic links are always traversed in this
1800 @node Recursive Retrieval Options, Recursive Accept/Reject Options, FTP Options, Invoking
1801 @section Recursive Retrieval Options
1806 Turn on recursive retrieving. @xref{Recursive Download}, for more
1807 details. The default maximum depth is 5.
1809 @item -l @var{depth}
1810 @itemx --level=@var{depth}
1811 Specify recursion maximum depth level @var{depth} (@pxref{Recursive
1814 @cindex proxy filling
1815 @cindex delete after retrieval
1816 @cindex filling proxy cache
1817 @item --delete-after
1818 This option tells Wget to delete every single file it downloads,
1819 @emph{after} having done so. It is useful for pre-fetching popular
1820 pages through a proxy, e.g.:
1823 wget -r -nd --delete-after http://whatever.com/~popular/page/
1826 The @samp{-r} option is to retrieve recursively, and @samp{-nd} to not
1829 Note that @samp{--delete-after} deletes files on the local machine. It
1830 does not issue the @samp{DELE} command to remote FTP sites, for
1831 instance. Also note that when @samp{--delete-after} is specified,
1832 @samp{--convert-links} is ignored, so @samp{.orig} files are simply not
1833 created in the first place.
1835 @cindex conversion of links
1836 @cindex link conversion
1838 @itemx --convert-links
1839 After the download is complete, convert the links in the document to
1840 make them suitable for local viewing. This affects not only the visible
1841 hyperlinks, but any part of the document that links to external content,
1842 such as embedded images, links to style sheets, hyperlinks to non-@sc{html}
1845 Each link will be changed in one of the two ways:
1849 The links to files that have been downloaded by Wget will be changed to
1850 refer to the file they point to as a relative link.
1852 Example: if the downloaded file @file{/foo/doc.html} links to
1853 @file{/bar/img.gif}, also downloaded, then the link in @file{doc.html}
1854 will be modified to point to @samp{../bar/img.gif}. This kind of
1855 transformation works reliably for arbitrary combinations of directories.
1858 The links to files that have not been downloaded by Wget will be changed
1859 to include host name and absolute path of the location they point to.
1861 Example: if the downloaded file @file{/foo/doc.html} links to
1862 @file{/bar/img.gif} (or to @file{../bar/img.gif}), then the link in
1863 @file{doc.html} will be modified to point to
1864 @file{http://@var{hostname}/bar/img.gif}.
1867 Because of this, local browsing works reliably: if a linked file was
1868 downloaded, the link will refer to its local name; if it was not
1869 downloaded, the link will refer to its full Internet address rather than
1870 presenting a broken link. The fact that the former links are converted
1871 to relative links ensures that you can move the downloaded hierarchy to
1874 Note that only at the end of the download can Wget know which links have
1875 been downloaded. Because of that, the work done by @samp{-k} will be
1876 performed at the end of all the downloads.
1878 @cindex backing up converted files
1880 @itemx --backup-converted
1881 When converting a file, back up the original version with a @samp{.orig}
1882 suffix. Affects the behavior of @samp{-N} (@pxref{HTTP Time-Stamping
1887 Turn on options suitable for mirroring. This option turns on recursion
1888 and time-stamping, sets infinite recursion depth and keeps @sc{ftp}
1889 directory listings. It is currently equivalent to
1890 @samp{-r -N -l inf --no-remove-listing}.
1892 @cindex page requisites
1893 @cindex required images, downloading
1895 @itemx --page-requisites
1896 This option causes Wget to download all the files that are necessary to
1897 properly display a given @sc{html} page. This includes such things as
1898 inlined images, sounds, and referenced stylesheets.
1900 Ordinarily, when downloading a single @sc{html} page, any requisite documents
1901 that may be needed to display it properly are not downloaded. Using
1902 @samp{-r} together with @samp{-l} can help, but since Wget does not
1903 ordinarily distinguish between external and inlined documents, one is
1904 generally left with ``leaf documents'' that are missing their
1907 For instance, say document @file{1.html} contains an @code{<IMG>} tag
1908 referencing @file{1.gif} and an @code{<A>} tag pointing to external
1909 document @file{2.html}. Say that @file{2.html} is similar but that its
1910 image is @file{2.gif} and it links to @file{3.html}. Say this
1911 continues up to some arbitrarily high number.
1913 If one executes the command:
1916 wget -r -l 2 http://@var{site}/1.html
1919 then @file{1.html}, @file{1.gif}, @file{2.html}, @file{2.gif}, and
1920 @file{3.html} will be downloaded. As you can see, @file{3.html} is
1921 without its requisite @file{3.gif} because Wget is simply counting the
1922 number of hops (up to 2) away from @file{1.html} in order to determine
1923 where to stop the recursion. However, with this command:
1926 wget -r -l 2 -p http://@var{site}/1.html
1929 all the above files @emph{and} @file{3.html}'s requisite @file{3.gif}
1930 will be downloaded. Similarly,
1933 wget -r -l 1 -p http://@var{site}/1.html
1936 will cause @file{1.html}, @file{1.gif}, @file{2.html}, and @file{2.gif}
1937 to be downloaded. One might think that:
1940 wget -r -l 0 -p http://@var{site}/1.html
1943 would download just @file{1.html} and @file{1.gif}, but unfortunately
1944 this is not the case, because @samp{-l 0} is equivalent to
1945 @samp{-l inf}---that is, infinite recursion. To download a single @sc{html}
1946 page (or a handful of them, all specified on the command-line or in a
1947 @samp{-i} @sc{url} input file) and its (or their) requisites, simply leave off
1948 @samp{-r} and @samp{-l}:
1951 wget -p http://@var{site}/1.html
1954 Note that Wget will behave as if @samp{-r} had been specified, but only
1955 that single page and its requisites will be downloaded. Links from that
1956 page to external documents will not be followed. Actually, to download
1957 a single page and all its requisites (even if they exist on separate
1958 websites), and make sure the lot displays properly locally, this author
1959 likes to use a few options in addition to @samp{-p}:
1962 wget -E -H -k -K -p http://@var{site}/@var{document}
1965 To finish off this topic, it's worth knowing that Wget's idea of an
1966 external document link is any URL specified in an @code{<A>} tag, an
1967 @code{<AREA>} tag, or a @code{<LINK>} tag other than @code{<LINK
1970 @cindex @sc{html} comments
1971 @cindex comments, @sc{html}
1972 @item --strict-comments
1973 Turn on strict parsing of @sc{html} comments. The default is to terminate
1974 comments at the first occurrence of @samp{-->}.
1976 According to specifications, @sc{html} comments are expressed as @sc{sgml}
1977 @dfn{declarations}. Declaration is special markup that begins with
1978 @samp{<!} and ends with @samp{>}, such as @samp{<!DOCTYPE ...>}, that
1979 may contain comments between a pair of @samp{--} delimiters. @sc{html}
1980 comments are ``empty declarations'', @sc{sgml} declarations without any
1981 non-comment text. Therefore, @samp{<!--foo-->} is a valid comment, and
1982 so is @samp{<!--one-- --two-->}, but @samp{<!--1--2-->} is not.
1984 On the other hand, most @sc{html} writers don't perceive comments as anything
1985 other than text delimited with @samp{<!--} and @samp{-->}, which is not
1986 quite the same. For example, something like @samp{<!------------>}
1987 works as a valid comment as long as the number of dashes is a multiple
1988 of four (!). If not, the comment technically lasts until the next
1989 @samp{--}, which may be at the other end of the document. Because of
1990 this, many popular browsers completely ignore the specification and
1991 implement what users have come to expect: comments delimited with
1992 @samp{<!--} and @samp{-->}.
1994 Until version 1.9, Wget interpreted comments strictly, which resulted in
1995 missing links in many web pages that displayed fine in browsers, but had
1996 the misfortune of containing non-compliant comments. Beginning with
1997 version 1.9, Wget has joined the ranks of clients that implements
1998 ``naive'' comments, terminating each comment at the first occurrence of
2001 If, for whatever reason, you want strict comment parsing, use this
2002 option to turn it on.
2005 @node Recursive Accept/Reject Options, Exit Status, Recursive Retrieval Options, Invoking
2006 @section Recursive Accept/Reject Options
2009 @item -A @var{acclist} --accept @var{acclist}
2010 @itemx -R @var{rejlist} --reject @var{rejlist}
2011 Specify comma-separated lists of file name suffixes or patterns to
2012 accept or reject (@pxref{Types of Files}). Note that if
2013 any of the wildcard characters, @samp{*}, @samp{?}, @samp{[} or
2014 @samp{]}, appear in an element of @var{acclist} or @var{rejlist},
2015 it will be treated as a pattern, rather than a suffix.
2017 @item -D @var{domain-list}
2018 @itemx --domains=@var{domain-list}
2019 Set domains to be followed. @var{domain-list} is a comma-separated list
2020 of domains. Note that it does @emph{not} turn on @samp{-H}.
2022 @item --exclude-domains @var{domain-list}
2023 Specify the domains that are @emph{not} to be followed
2024 (@pxref{Spanning Hosts}).
2026 @cindex follow FTP links
2028 Follow @sc{ftp} links from @sc{html} documents. Without this option,
2029 Wget will ignore all the @sc{ftp} links.
2031 @cindex tag-based recursive pruning
2032 @item --follow-tags=@var{list}
2033 Wget has an internal table of @sc{html} tag / attribute pairs that it
2034 considers when looking for linked documents during a recursive
2035 retrieval. If a user wants only a subset of those tags to be
2036 considered, however, he or she should be specify such tags in a
2037 comma-separated @var{list} with this option.
2039 @item --ignore-tags=@var{list}
2040 This is the opposite of the @samp{--follow-tags} option. To skip
2041 certain @sc{html} tags when recursively looking for documents to download,
2042 specify them in a comma-separated @var{list}.
2044 In the past, this option was the best bet for downloading a single page
2045 and its requisites, using a command-line like:
2048 wget --ignore-tags=a,area -H -k -K -r http://@var{site}/@var{document}
2051 However, the author of this option came across a page with tags like
2052 @code{<LINK REL="home" HREF="/">} and came to the realization that
2053 specifying tags to ignore was not enough. One can't just tell Wget to
2054 ignore @code{<LINK>}, because then stylesheets will not be downloaded.
2055 Now the best bet for downloading a single page and its requisites is the
2056 dedicated @samp{--page-requisites} option.
2061 Ignore case when matching files and directories. This influences the
2062 behavior of -R, -A, -I, and -X options, as well as globbing
2063 implemented when downloading from FTP sites. For example, with this
2064 option, @samp{-A *.txt} will match @samp{file1.txt}, but also
2065 @samp{file2.TXT}, @samp{file3.TxT}, and so on.
2069 Enable spanning across hosts when doing recursive retrieving
2070 (@pxref{Spanning Hosts}).
2074 Follow relative links only. Useful for retrieving a specific home page
2075 without any distractions, not even those from the same hosts
2076 (@pxref{Relative Links}).
2079 @itemx --include-directories=@var{list}
2080 Specify a comma-separated list of directories you wish to follow when
2081 downloading (@pxref{Directory-Based Limits}). Elements
2082 of @var{list} may contain wildcards.
2085 @itemx --exclude-directories=@var{list}
2086 Specify a comma-separated list of directories you wish to exclude from
2087 download (@pxref{Directory-Based Limits}). Elements of
2088 @var{list} may contain wildcards.
2092 Do not ever ascend to the parent directory when retrieving recursively.
2093 This is a useful option, since it guarantees that only the files
2094 @emph{below} a certain hierarchy will be downloaded.
2095 @xref{Directory-Based Limits}, for more details.
2100 @node Exit Status, , Recursive Accept/Reject Options, Invoking
2101 @section Exit Status
2103 @c man begin EXITSTATUS
2105 Wget may return one of several error codes if it encounters problems.
2110 No problems occurred.
2116 Parse error---for instance, when parsing command-line options, the
2117 @samp{.wgetrc} or @samp{.netrc}...
2126 SSL verification failure.
2129 Username/password authentication failure.
2135 Server issued an error response.
2139 With the exceptions of 0 and 1, the lower-numbered exit codes take
2140 precedence over higher-numbered ones, when multiple types of errors
2143 In versions of Wget prior to 1.12, Wget's exit status tended to be
2144 unhelpful and inconsistent. Recursive downloads would virtually always
2145 return 0 (success), regardless of any issues encountered, and
2146 non-recursive fetches only returned the status corresponding to the
2147 most recently-attempted download.
2151 @node Recursive Download, Following Links, Invoking, Top
2152 @chapter Recursive Download
2155 @cindex recursive download
2157 GNU Wget is capable of traversing parts of the Web (or a single
2158 @sc{http} or @sc{ftp} server), following links and directory structure.
2159 We refer to this as to @dfn{recursive retrieval}, or @dfn{recursion}.
2161 With @sc{http} @sc{url}s, Wget retrieves and parses the @sc{html} or
2162 @sc{css} from the given @sc{url}, retrieving the files the document
2163 refers to, through markup like @code{href} or @code{src}, or @sc{css}
2164 @sc{uri} values specified using the @samp{url()} functional notation.
2165 If the freshly downloaded file is also of type @code{text/html},
2166 @code{application/xhtml+xml}, or @code{text/css}, it will be parsed
2167 and followed further.
2169 Recursive retrieval of @sc{http} and @sc{html}/@sc{css} content is
2170 @dfn{breadth-first}. This means that Wget first downloads the requested
2171 document, then the documents linked from that document, then the
2172 documents linked by them, and so on. In other words, Wget first
2173 downloads the documents at depth 1, then those at depth 2, and so on
2174 until the specified maximum depth.
2176 The maximum @dfn{depth} to which the retrieval may descend is specified
2177 with the @samp{-l} option. The default maximum depth is five layers.
2179 When retrieving an @sc{ftp} @sc{url} recursively, Wget will retrieve all
2180 the data from the given directory tree (including the subdirectories up
2181 to the specified depth) on the remote server, creating its mirror image
2182 locally. @sc{ftp} retrieval is also limited by the @code{depth}
2183 parameter. Unlike @sc{http} recursion, @sc{ftp} recursion is performed
2186 By default, Wget will create a local directory tree, corresponding to
2187 the one found on the remote server.
2189 Recursive retrieving can find a number of applications, the most
2190 important of which is mirroring. It is also useful for @sc{www}
2191 presentations, and any other opportunities where slow network
2192 connections should be bypassed by storing the files locally.
2194 You should be warned that recursive downloads can overload the remote
2195 servers. Because of that, many administrators frown upon them and may
2196 ban access from your site if they detect very fast downloads of big
2197 amounts of content. When downloading from Internet servers, consider
2198 using the @samp{-w} option to introduce a delay between accesses to the
2199 server. The download will take a while longer, but the server
2200 administrator will not be alarmed by your rudeness.
2202 Of course, recursive download may cause problems on your machine. If
2203 left to run unchecked, it can easily fill up the disk. If downloading
2204 from local network, it can also take bandwidth on the system, as well as
2205 consume memory and CPU.
2207 Try to specify the criteria that match the kind of download you are
2208 trying to achieve. If you want to download only one page, use
2209 @samp{--page-requisites} without any additional recursion. If you want
2210 to download things under one directory, use @samp{-np} to avoid
2211 downloading things from other directories. If you want to download all
2212 the files from one directory, use @samp{-l 1} to make sure the recursion
2213 depth never exceeds one. @xref{Following Links}, for more information
2216 Recursive retrieval should be used with care. Don't say you were not
2219 @node Following Links, Time-Stamping, Recursive Download, Top
2220 @chapter Following Links
2222 @cindex following links
2224 When retrieving recursively, one does not wish to retrieve loads of
2225 unnecessary data. Most of the time the users bear in mind exactly what
2226 they want to download, and want Wget to follow only specific links.
2228 For example, if you wish to download the music archive from
2229 @samp{fly.srk.fer.hr}, you will not want to download all the home pages
2230 that happen to be referenced by an obscure part of the archive.
2232 Wget possesses several mechanisms that allows you to fine-tune which
2233 links it will follow.
2236 * Spanning Hosts:: (Un)limiting retrieval based on host name.
2237 * Types of Files:: Getting only certain files.
2238 * Directory-Based Limits:: Getting only certain directories.
2239 * Relative Links:: Follow relative links only.
2240 * FTP Links:: Following FTP links.
2243 @node Spanning Hosts, Types of Files, Following Links, Following Links
2244 @section Spanning Hosts
2245 @cindex spanning hosts
2246 @cindex hosts, spanning
2248 Wget's recursive retrieval normally refuses to visit hosts different
2249 than the one you specified on the command line. This is a reasonable
2250 default; without it, every retrieval would have the potential to turn
2251 your Wget into a small version of google.
2253 However, visiting different hosts, or @dfn{host spanning,} is sometimes
2254 a useful option. Maybe the images are served from a different server.
2255 Maybe you're mirroring a site that consists of pages interlinked between
2256 three servers. Maybe the server has two equivalent names, and the @sc{html}
2257 pages refer to both interchangeably.
2260 @item Span to any host---@samp{-H}
2262 The @samp{-H} option turns on host spanning, thus allowing Wget's
2263 recursive run to visit any host referenced by a link. Unless sufficient
2264 recursion-limiting criteria are applied depth, these foreign hosts will
2265 typically link to yet more hosts, and so on until Wget ends up sucking
2266 up much more data than you have intended.
2268 @item Limit spanning to certain domains---@samp{-D}
2270 The @samp{-D} option allows you to specify the domains that will be
2271 followed, thus limiting the recursion only to the hosts that belong to
2272 these domains. Obviously, this makes sense only in conjunction with
2273 @samp{-H}. A typical example would be downloading the contents of
2274 @samp{www.server.com}, but allowing downloads from
2275 @samp{images.server.com}, etc.:
2278 wget -rH -Dserver.com http://www.server.com/
2281 You can specify more than one address by separating them with a comma,
2282 e.g. @samp{-Ddomain1.com,domain2.com}.
2284 @item Keep download off certain domains---@samp{--exclude-domains}
2286 If there are domains you want to exclude specifically, you can do it
2287 with @samp{--exclude-domains}, which accepts the same type of arguments
2288 of @samp{-D}, but will @emph{exclude} all the listed domains. For
2289 example, if you want to download all the hosts from @samp{foo.edu}
2290 domain, with the exception of @samp{sunsite.foo.edu}, you can do it like
2294 wget -rH -Dfoo.edu --exclude-domains sunsite.foo.edu \
2300 @node Types of Files, Directory-Based Limits, Spanning Hosts, Following Links
2301 @section Types of Files
2302 @cindex types of files
2304 When downloading material from the web, you will often want to restrict
2305 the retrieval to only certain file types. For example, if you are
2306 interested in downloading @sc{gif}s, you will not be overjoyed to get
2307 loads of PostScript documents, and vice versa.
2309 Wget offers two options to deal with this problem. Each option
2310 description lists a short name, a long name, and the equivalent command
2313 @cindex accept wildcards
2314 @cindex accept suffixes
2315 @cindex wildcards, accept
2316 @cindex suffixes, accept
2318 @item -A @var{acclist}
2319 @itemx --accept @var{acclist}
2320 @itemx accept = @var{acclist}
2321 @itemx --accept-regex @var{urlregex}
2322 @itemx accept-regex = @var{urlregex}
2323 The argument to @samp{--accept} option is a list of file suffixes or
2324 patterns that Wget will download during recursive retrieval. A suffix
2325 is the ending part of a file, and consists of ``normal'' letters,
2326 e.g. @samp{gif} or @samp{.jpg}. A matching pattern contains shell-like
2327 wildcards, e.g. @samp{books*} or @samp{zelazny*196[0-9]*}.
2329 So, specifying @samp{wget -A gif,jpg} will make Wget download only the
2330 files ending with @samp{gif} or @samp{jpg}, i.e. @sc{gif}s and
2331 @sc{jpeg}s. On the other hand, @samp{wget -A "zelazny*196[0-9]*"} will
2332 download only files beginning with @samp{zelazny} and containing numbers
2333 from 1960 to 1969 anywhere within. Look up the manual of your shell for
2334 a description of how pattern matching works.
2336 Of course, any number of suffixes and patterns can be combined into a
2337 comma-separated list, and given as an argument to @samp{-A}.
2339 The argument to @samp{--accept-regex} option is a regular expression which
2340 is matched against the complete URL.
2342 @cindex reject wildcards
2343 @cindex reject suffixes
2344 @cindex wildcards, reject
2345 @cindex suffixes, reject
2346 @item -R @var{rejlist}
2347 @itemx --reject @var{rejlist}
2348 @itemx reject = @var{rejlist}
2349 @itemx --reject-regex @var{urlregex}
2350 @itemx reject-regex = @var{urlregex}
2351 The @samp{--reject} option works the same way as @samp{--accept}, only
2352 its logic is the reverse; Wget will download all files @emph{except} the
2353 ones matching the suffixes (or patterns) in the list.
2355 So, if you want to download a whole page except for the cumbersome
2356 @sc{mpeg}s and @sc{.au} files, you can use @samp{wget -R mpg,mpeg,au}.
2357 Analogously, to download all files except the ones beginning with
2358 @samp{bjork}, use @samp{wget -R "bjork*"}. The quotes are to prevent
2359 expansion by the shell.
2362 The argument to @samp{--accept-regex} option is a regular expression which
2363 is matched against the complete URL.
2366 The @samp{-A} and @samp{-R} options may be combined to achieve even
2367 better fine-tuning of which files to retrieve. E.g. @samp{wget -A
2368 "*zelazny*" -R .ps} will download all the files having @samp{zelazny} as
2369 a part of their name, but @emph{not} the PostScript files.
2371 Note that these two options do not affect the downloading of @sc{html}
2372 files (as determined by a @samp{.htm} or @samp{.html} filename
2373 prefix). This behavior may not be desirable for all users, and may be
2374 changed for future versions of Wget.
2376 Note, too, that query strings (strings at the end of a URL beginning
2377 with a question mark (@samp{?}) are not included as part of the
2378 filename for accept/reject rules, even though these will actually
2379 contribute to the name chosen for the local file. It is expected that
2380 a future version of Wget will provide an option to allow matching
2381 against query strings.
2383 Finally, it's worth noting that the accept/reject lists are matched
2384 @emph{twice} against downloaded files: once against the URL's filename
2385 portion, to determine if the file should be downloaded in the first
2386 place; then, after it has been accepted and successfully downloaded,
2387 the local file's name is also checked against the accept/reject lists
2388 to see if it should be removed. The rationale was that, since
2389 @samp{.htm} and @samp{.html} files are always downloaded regardless of
2390 accept/reject rules, they should be removed @emph{after} being
2391 downloaded and scanned for links, if they did match the accept/reject
2392 lists. However, this can lead to unexpected results, since the local
2393 filenames can differ from the original URL filenames in the following
2394 ways, all of which can change whether an accept/reject rule matches:
2398 If the local file already exists and @samp{--no-directories} was
2399 specified, a numeric suffix will be appended to the original name.
2401 If @samp{--adjust-extension} was specified, the local filename might have
2402 @samp{.html} appended to it. If Wget is invoked with @samp{-E -A.php},
2403 a filename such as @samp{index.php} will match be accepted, but upon
2404 download will be named @samp{index.php.html}, which no longer matches,
2405 and so the file will be deleted.
2407 Query strings do not contribute to URL matching, but are included in
2408 local filenames, and so @emph{do} contribute to filename matching.
2412 This behavior, too, is considered less-than-desirable, and may change
2413 in a future version of Wget.
2415 @node Directory-Based Limits, Relative Links, Types of Files, Following Links
2416 @section Directory-Based Limits
2418 @cindex directory limits
2420 Regardless of other link-following facilities, it is often useful to
2421 place the restriction of what files to retrieve based on the directories
2422 those files are placed in. There can be many reasons for this---the
2423 home pages may be organized in a reasonable directory structure; or some
2424 directories may contain useless information, e.g. @file{/cgi-bin} or
2425 @file{/dev} directories.
2427 Wget offers three different options to deal with this requirement. Each
2428 option description lists a short name, a long name, and the equivalent
2429 command in @file{.wgetrc}.
2431 @cindex directories, include
2432 @cindex include directories
2433 @cindex accept directories
2436 @itemx --include @var{list}
2437 @itemx include_directories = @var{list}
2438 @samp{-I} option accepts a comma-separated list of directories included
2439 in the retrieval. Any other directories will simply be ignored. The
2440 directories are absolute paths.
2442 So, if you wish to download from @samp{http://host/people/bozo/}
2443 following only links to bozo's colleagues in the @file{/people}
2444 directory and the bogus scripts in @file{/cgi-bin}, you can specify:
2447 wget -I /people,/cgi-bin http://host/people/bozo/
2450 @cindex directories, exclude
2451 @cindex exclude directories
2452 @cindex reject directories
2454 @itemx --exclude @var{list}
2455 @itemx exclude_directories = @var{list}
2456 @samp{-X} option is exactly the reverse of @samp{-I}---this is a list of
2457 directories @emph{excluded} from the download. E.g. if you do not want
2458 Wget to download things from @file{/cgi-bin} directory, specify @samp{-X
2459 /cgi-bin} on the command line.
2461 The same as with @samp{-A}/@samp{-R}, these two options can be combined
2462 to get a better fine-tuning of downloading subdirectories. E.g. if you
2463 want to load all the files from @file{/pub} hierarchy except for
2464 @file{/pub/worthless}, specify @samp{-I/pub -X/pub/worthless}.
2469 @itemx no_parent = on
2470 The simplest, and often very useful way of limiting directories is
2471 disallowing retrieval of the links that refer to the hierarchy
2472 @dfn{above} than the beginning directory, i.e. disallowing ascent to the
2473 parent directory/directories.
2475 The @samp{--no-parent} option (short @samp{-np}) is useful in this case.
2476 Using it guarantees that you will never leave the existing hierarchy.
2477 Supposing you issue Wget with:
2480 wget -r --no-parent http://somehost/~luzer/my-archive/
2483 You may rest assured that none of the references to
2484 @file{/~his-girls-homepage/} or @file{/~luzer/all-my-mpegs/} will be
2485 followed. Only the archive you are interested in will be downloaded.
2486 Essentially, @samp{--no-parent} is similar to
2487 @samp{-I/~luzer/my-archive}, only it handles redirections in a more
2488 intelligent fashion.
2490 @strong{Note} that, for HTTP (and HTTPS), the trailing slash is very
2491 important to @samp{--no-parent}. HTTP has no concept of a ``directory''---Wget
2492 relies on you to indicate what's a directory and what isn't. In
2493 @samp{http://foo/bar/}, Wget will consider @samp{bar} to be a
2494 directory, while in @samp{http://foo/bar} (no trailing slash),
2495 @samp{bar} will be considered a filename (so @samp{--no-parent} would be
2496 meaningless, as its parent is @samp{/}).
2499 @node Relative Links, FTP Links, Directory-Based Limits, Following Links
2500 @section Relative Links
2501 @cindex relative links
2503 When @samp{-L} is turned on, only the relative links are ever followed.
2504 Relative links are here defined those that do not refer to the web
2505 server root. For example, these links are relative:
2509 <a href="foo/bar.gif">
2510 <a href="../foo/bar.gif">
2513 These links are not relative:
2517 <a href="/foo/bar.gif">
2518 <a href="http://www.server.com/foo/bar.gif">
2521 Using this option guarantees that recursive retrieval will not span
2522 hosts, even without @samp{-H}. In simple cases it also allows downloads
2523 to ``just work'' without having to convert links.
2525 This option is probably not very useful and might be removed in a future
2528 @node FTP Links, , Relative Links, Following Links
2529 @section Following FTP Links
2530 @cindex following ftp links
2532 The rules for @sc{ftp} are somewhat specific, as it is necessary for
2533 them to be. @sc{ftp} links in @sc{html} documents are often included
2534 for purposes of reference, and it is often inconvenient to download them
2537 To have @sc{ftp} links followed from @sc{html} documents, you need to
2538 specify the @samp{--follow-ftp} option. Having done that, @sc{ftp}
2539 links will span hosts regardless of @samp{-H} setting. This is logical,
2540 as @sc{ftp} links rarely point to the same host where the @sc{http}
2541 server resides. For similar reasons, the @samp{-L} options has no
2542 effect on such downloads. On the other hand, domain acceptance
2543 (@samp{-D}) and suffix rules (@samp{-A} and @samp{-R}) apply normally.
2545 Also note that followed links to @sc{ftp} directories will not be
2546 retrieved recursively further.
2548 @node Time-Stamping, Startup File, Following Links, Top
2549 @chapter Time-Stamping
2550 @cindex time-stamping
2551 @cindex timestamping
2552 @cindex updating the archives
2553 @cindex incremental updating
2555 One of the most important aspects of mirroring information from the
2556 Internet is updating your archives.
2558 Downloading the whole archive again and again, just to replace a few
2559 changed files is expensive, both in terms of wasted bandwidth and money,
2560 and the time to do the update. This is why all the mirroring tools
2561 offer the option of incremental updating.
2563 Such an updating mechanism means that the remote server is scanned in
2564 search of @dfn{new} files. Only those new files will be downloaded in
2565 the place of the old ones.
2567 A file is considered new if one of these two conditions are met:
2571 A file of that name does not already exist locally.
2574 A file of that name does exist, but the remote file was modified more
2575 recently than the local file.
2578 To implement this, the program needs to be aware of the time of last
2579 modification of both local and remote files. We call this information the
2580 @dfn{time-stamp} of a file.
2582 The time-stamping in GNU Wget is turned on using @samp{--timestamping}
2583 (@samp{-N}) option, or through @code{timestamping = on} directive in
2584 @file{.wgetrc}. With this option, for each file it intends to download,
2585 Wget will check whether a local file of the same name exists. If it
2586 does, and the remote file is not newer, Wget will not download it.
2588 If the local file does not exist, or the sizes of the files do not
2589 match, Wget will download the remote file no matter what the time-stamps
2593 * Time-Stamping Usage::
2594 * HTTP Time-Stamping Internals::
2595 * FTP Time-Stamping Internals::
2598 @node Time-Stamping Usage, HTTP Time-Stamping Internals, Time-Stamping, Time-Stamping
2599 @section Time-Stamping Usage
2600 @cindex time-stamping usage
2601 @cindex usage, time-stamping
2603 The usage of time-stamping is simple. Say you would like to download a
2604 file so that it keeps its date of modification.
2607 wget -S http://www.gnu.ai.mit.edu/
2610 A simple @code{ls -l} shows that the time stamp on the local file equals
2611 the state of the @code{Last-Modified} header, as returned by the server.
2612 As you can see, the time-stamping info is preserved locally, even
2613 without @samp{-N} (at least for @sc{http}).
2615 Several days later, you would like Wget to check if the remote file has
2616 changed, and download it if it has.
2619 wget -N http://www.gnu.ai.mit.edu/
2622 Wget will ask the server for the last-modified date. If the local file
2623 has the same timestamp as the server, or a newer one, the remote file
2624 will not be re-fetched. However, if the remote file is more recent,
2625 Wget will proceed to fetch it.
2627 The same goes for @sc{ftp}. For example:
2630 wget "ftp://ftp.ifi.uio.no/pub/emacs/gnus/*"
2633 (The quotes around that URL are to prevent the shell from trying to
2634 interpret the @samp{*}.)
2636 After download, a local directory listing will show that the timestamps
2637 match those on the remote server. Reissuing the command with @samp{-N}
2638 will make Wget re-fetch @emph{only} the files that have been modified
2639 since the last download.
2641 If you wished to mirror the GNU archive every week, you would use a
2642 command like the following, weekly:
2645 wget --timestamping -r ftp://ftp.gnu.org/pub/gnu/
2648 Note that time-stamping will only work for files for which the server
2649 gives a timestamp. For @sc{http}, this depends on getting a
2650 @code{Last-Modified} header. For @sc{ftp}, this depends on getting a
2651 directory listing with dates in a format that Wget can parse
2652 (@pxref{FTP Time-Stamping Internals}).
2654 @node HTTP Time-Stamping Internals, FTP Time-Stamping Internals, Time-Stamping Usage, Time-Stamping
2655 @section HTTP Time-Stamping Internals
2656 @cindex http time-stamping
2658 Time-stamping in @sc{http} is implemented by checking of the
2659 @code{Last-Modified} header. If you wish to retrieve the file
2660 @file{foo.html} through @sc{http}, Wget will check whether
2661 @file{foo.html} exists locally. If it doesn't, @file{foo.html} will be
2662 retrieved unconditionally.
2664 If the file does exist locally, Wget will first check its local
2665 time-stamp (similar to the way @code{ls -l} checks it), and then send a
2666 @code{HEAD} request to the remote server, demanding the information on
2669 The @code{Last-Modified} header is examined to find which file was
2670 modified more recently (which makes it ``newer''). If the remote file
2671 is newer, it will be downloaded; if it is older, Wget will give
2672 up.@footnote{As an additional check, Wget will look at the
2673 @code{Content-Length} header, and compare the sizes; if they are not the
2674 same, the remote file will be downloaded no matter what the time-stamp
2677 When @samp{--backup-converted} (@samp{-K}) is specified in conjunction
2678 with @samp{-N}, server file @samp{@var{X}} is compared to local file
2679 @samp{@var{X}.orig}, if extant, rather than being compared to local file
2680 @samp{@var{X}}, which will always differ if it's been converted by
2681 @samp{--convert-links} (@samp{-k}).
2683 Arguably, @sc{http} time-stamping should be implemented using the
2684 @code{If-Modified-Since} request.
2686 @node FTP Time-Stamping Internals, , HTTP Time-Stamping Internals, Time-Stamping
2687 @section FTP Time-Stamping Internals
2688 @cindex ftp time-stamping
2690 In theory, @sc{ftp} time-stamping works much the same as @sc{http}, only
2691 @sc{ftp} has no headers---time-stamps must be ferreted out of directory
2694 If an @sc{ftp} download is recursive or uses globbing, Wget will use the
2695 @sc{ftp} @code{LIST} command to get a file listing for the directory
2696 containing the desired file(s). It will try to analyze the listing,
2697 treating it like Unix @code{ls -l} output, extracting the time-stamps.
2698 The rest is exactly the same as for @sc{http}. Note that when
2699 retrieving individual files from an @sc{ftp} server without using
2700 globbing or recursion, listing files will not be downloaded (and thus
2701 files will not be time-stamped) unless @samp{-N} is specified.
2703 Assumption that every directory listing is a Unix-style listing may
2704 sound extremely constraining, but in practice it is not, as many
2705 non-Unix @sc{ftp} servers use the Unixoid listing format because most
2706 (all?) of the clients understand it. Bear in mind that @sc{rfc959}
2707 defines no standard way to get a file list, let alone the time-stamps.
2708 We can only hope that a future standard will define this.
2710 Another non-standard solution includes the use of @code{MDTM} command
2711 that is supported by some @sc{ftp} servers (including the popular
2712 @code{wu-ftpd}), which returns the exact time of the specified file.
2713 Wget may support this command in the future.
2715 @node Startup File, Examples, Time-Stamping, Top
2716 @chapter Startup File
2717 @cindex startup file
2723 Once you know how to change default settings of Wget through command
2724 line arguments, you may wish to make some of those settings permanent.
2725 You can do that in a convenient way by creating the Wget startup
2726 file---@file{.wgetrc}.
2728 Besides @file{.wgetrc} is the ``main'' initialization file, it is
2729 convenient to have a special facility for storing passwords. Thus Wget
2730 reads and interprets the contents of @file{$HOME/.netrc}, if it finds
2731 it. You can find @file{.netrc} format in your system manuals.
2733 Wget reads @file{.wgetrc} upon startup, recognizing a limited set of
2737 * Wgetrc Location:: Location of various wgetrc files.
2738 * Wgetrc Syntax:: Syntax of wgetrc.
2739 * Wgetrc Commands:: List of available commands.
2740 * Sample Wgetrc:: A wgetrc example.
2743 @node Wgetrc Location, Wgetrc Syntax, Startup File, Startup File
2744 @section Wgetrc Location
2745 @cindex wgetrc location
2746 @cindex location of wgetrc
2748 When initializing, Wget will look for a @dfn{global} startup file,
2749 @file{/usr/local/etc/wgetrc} by default (or some prefix other than
2750 @file{/usr/local}, if Wget was not installed there) and read commands
2751 from there, if it exists.
2753 Then it will look for the user's file. If the environmental variable
2754 @code{WGETRC} is set, Wget will try to load that file. Failing that, no
2755 further attempts will be made.
2757 If @code{WGETRC} is not set, Wget will try to load @file{$HOME/.wgetrc}.
2759 The fact that user's settings are loaded after the system-wide ones
2760 means that in case of collision user's wgetrc @emph{overrides} the
2761 system-wide wgetrc (in @file{/usr/local/etc/wgetrc} by default).
2762 Fascist admins, away!
2764 @node Wgetrc Syntax, Wgetrc Commands, Wgetrc Location, Startup File
2765 @section Wgetrc Syntax
2766 @cindex wgetrc syntax
2767 @cindex syntax of wgetrc
2769 The syntax of a wgetrc command is simple:
2775 The @dfn{variable} will also be called @dfn{command}. Valid
2776 @dfn{values} are different for different commands.
2778 The commands are case-insensitive and underscore-insensitive. Thus
2779 @samp{DIr__PrefiX} is the same as @samp{dirprefix}. Empty lines, lines
2780 beginning with @samp{#} and lines containing white-space only are
2783 Commands that expect a comma-separated list will clear the list on an
2784 empty command. So, if you wish to reset the rejection list specified in
2785 global @file{wgetrc}, you can do it with:
2791 @node Wgetrc Commands, Sample Wgetrc, Wgetrc Syntax, Startup File
2792 @section Wgetrc Commands
2793 @cindex wgetrc commands
2795 The complete set of commands is listed below. Legal values are listed
2796 after the @samp{=}. Simple Boolean values can be set or unset using
2797 @samp{on} and @samp{off} or @samp{1} and @samp{0}.
2799 Some commands take pseudo-arbitrary values. @var{address} values can be
2800 hostnames or dotted-quad IP addresses. @var{n} can be any positive
2801 integer, or @samp{inf} for infinity, where appropriate. @var{string}
2802 values can be any non-empty string.
2804 Most of these commands have direct command-line equivalents. Also, any
2805 wgetrc command can be specified on the command line using the
2806 @samp{--execute} switch (@pxref{Basic Startup Options}.)
2809 @item accept/reject = @var{string}
2810 Same as @samp{-A}/@samp{-R} (@pxref{Types of Files}).
2812 @item add_hostdir = on/off
2813 Enable/disable host-prefixed file names. @samp{-nH} disables it.
2815 @item ask_password = on/off
2816 Prompt for a password for each connection established. Cannot be specified
2817 when @samp{--password} is being used, because they are mutually
2818 exclusive. Equivalent to @samp{--ask-password}.
2820 @item auth_no_challenge = on/off
2821 If this option is given, Wget will send Basic HTTP authentication
2822 information (plaintext username and password) for all requests. See
2823 @samp{--auth-no-challenge}.
2825 @item background = on/off
2826 Enable/disable going to background---the same as @samp{-b} (which
2829 @item backup_converted = on/off
2830 Enable/disable saving pre-converted files with the suffix
2831 @samp{.orig}---the same as @samp{-K} (which enables it).
2833 @c @item backups = @var{number}
2834 @c #### Document me!
2836 @item base = @var{string}
2837 Consider relative @sc{url}s in input files (specified via the
2838 @samp{input} command or the @samp{--input-file}/@samp{-i} option,
2839 together with @samp{force_html} or @samp{--force-html})
2840 as being relative to @var{string}---the same as @samp{--base=@var{string}}.
2842 @item bind_address = @var{address}
2843 Bind to @var{address}, like the @samp{--bind-address=@var{address}}.
2845 @item ca_certificate = @var{file}
2846 Set the certificate authority bundle file to @var{file}. The same
2847 as @samp{--ca-certificate=@var{file}}.
2849 @item ca_directory = @var{directory}
2850 Set the directory used for certificate authorities. The same as
2851 @samp{--ca-directory=@var{directory}}.
2853 @item cache = on/off
2854 When set to off, disallow server-caching. See the @samp{--no-cache}
2857 @item certificate = @var{file}
2858 Set the client certificate file name to @var{file}. The same as
2859 @samp{--certificate=@var{file}}.
2861 @item certificate_type = @var{string}
2862 Specify the type of the client certificate, legal values being
2863 @samp{PEM} (the default) and @samp{DER} (aka ASN1). The same as
2864 @samp{--certificate-type=@var{string}}.
2866 @item check_certificate = on/off
2867 If this is set to off, the server certificate is not checked against
2868 the specified client authorities. The default is ``on''. The same as
2869 @samp{--check-certificate}.
2871 @item connect_timeout = @var{n}
2872 Set the connect timeout---the same as @samp{--connect-timeout}.
2874 @item content_disposition = on/off
2875 Turn on recognition of the (non-standard) @samp{Content-Disposition}
2876 HTTP header---if set to @samp{on}, the same as @samp{--content-disposition}.
2878 @item trust_server_names = on/off
2879 If set to on, use the last component of a redirection URL for the local
2882 @item continue = on/off
2883 If set to on, force continuation of preexistent partially retrieved
2884 files. See @samp{-c} before setting it.
2886 @item convert_links = on/off
2887 Convert non-relative links locally. The same as @samp{-k}.
2889 @item cookies = on/off
2890 When set to off, disallow cookies. See the @samp{--cookies} option.
2892 @item cut_dirs = @var{n}
2893 Ignore @var{n} remote directory components. Equivalent to
2894 @samp{--cut-dirs=@var{n}}.
2896 @item debug = on/off
2897 Debug mode, same as @samp{-d}.
2899 @item default_page = @var{string}
2900 Default page name---the same as @samp{--default-page=@var{string}}.
2902 @item delete_after = on/off
2903 Delete after download---the same as @samp{--delete-after}.
2905 @item dir_prefix = @var{string}
2906 Top of directory tree---the same as @samp{-P @var{string}}.
2908 @item dirstruct = on/off
2909 Turning dirstruct on or off---the same as @samp{-x} or @samp{-nd},
2912 @item dns_cache = on/off
2913 Turn DNS caching on/off. Since DNS caching is on by default, this
2914 option is normally used to turn it off and is equivalent to
2915 @samp{--no-dns-cache}.
2917 @item dns_timeout = @var{n}
2918 Set the DNS timeout---the same as @samp{--dns-timeout}.
2920 @item domains = @var{string}
2921 Same as @samp{-D} (@pxref{Spanning Hosts}).
2923 @item dot_bytes = @var{n}
2924 Specify the number of bytes ``contained'' in a dot, as seen throughout
2925 the retrieval (1024 by default). You can postfix the value with
2926 @samp{k} or @samp{m}, representing kilobytes and megabytes,
2927 respectively. With dot settings you can tailor the dot retrieval to
2928 suit your needs, or you can use the predefined @dfn{styles}
2929 (@pxref{Download Options}).
2931 @item dot_spacing = @var{n}
2932 Specify the number of dots in a single cluster (10 by default).
2934 @item dots_in_line = @var{n}
2935 Specify the number of dots that will be printed in each line throughout
2936 the retrieval (50 by default).
2938 @item egd_file = @var{file}
2939 Use @var{string} as the EGD socket file name. The same as
2940 @samp{--egd-file=@var{file}}.
2942 @item exclude_directories = @var{string}
2943 Specify a comma-separated list of directories you wish to exclude from
2944 download---the same as @samp{-X @var{string}} (@pxref{Directory-Based
2947 @item exclude_domains = @var{string}
2948 Same as @samp{--exclude-domains=@var{string}} (@pxref{Spanning
2951 @item follow_ftp = on/off
2952 Follow @sc{ftp} links from @sc{html} documents---the same as
2953 @samp{--follow-ftp}.
2955 @item follow_tags = @var{string}
2956 Only follow certain @sc{html} tags when doing a recursive retrieval,
2957 just like @samp{--follow-tags=@var{string}}.
2959 @item force_html = on/off
2960 If set to on, force the input filename to be regarded as an @sc{html}
2961 document---the same as @samp{-F}.
2963 @item ftp_password = @var{string}
2964 Set your @sc{ftp} password to @var{string}. Without this setting, the
2965 password defaults to @samp{-wget@@}, which is a useful default for
2966 anonymous @sc{ftp} access.
2968 This command used to be named @code{passwd} prior to Wget 1.10.
2970 @item ftp_proxy = @var{string}
2971 Use @var{string} as @sc{ftp} proxy, instead of the one specified in
2974 @item ftp_user = @var{string}
2975 Set @sc{ftp} user to @var{string}.
2977 This command used to be named @code{login} prior to Wget 1.10.
2980 Turn globbing on/off---the same as @samp{--glob} and @samp{--no-glob}.
2982 @item header = @var{string}
2983 Define a header for HTTP downloads, like using
2984 @samp{--header=@var{string}}.
2986 @item adjust_extension = on/off
2987 Add a @samp{.html} extension to @samp{text/html} or
2988 @samp{application/xhtml+xml} files that lack one, or a @samp{.css}
2989 extension to @samp{text/css} files that lack one, like
2990 @samp{-E}. Previously named @samp{html_extension} (still acceptable,
2993 @item http_keep_alive = on/off
2994 Turn the keep-alive feature on or off (defaults to on). Turning it
2995 off is equivalent to @samp{--no-http-keep-alive}.
2997 @item http_password = @var{string}
2998 Set @sc{http} password, equivalent to
2999 @samp{--http-password=@var{string}}.
3001 @item http_proxy = @var{string}
3002 Use @var{string} as @sc{http} proxy, instead of the one specified in
3005 @item http_user = @var{string}
3006 Set @sc{http} user to @var{string}, equivalent to
3007 @samp{--http-user=@var{string}}.
3009 @item https_proxy = @var{string}
3010 Use @var{string} as @sc{https} proxy, instead of the one specified in
3013 @item ignore_case = on/off
3014 When set to on, match files and directories case insensitively; the
3015 same as @samp{--ignore-case}.
3017 @item ignore_length = on/off
3018 When set to on, ignore @code{Content-Length} header; the same as
3019 @samp{--ignore-length}.
3021 @item ignore_tags = @var{string}
3022 Ignore certain @sc{html} tags when doing a recursive retrieval, like
3023 @samp{--ignore-tags=@var{string}}.
3025 @item include_directories = @var{string}
3026 Specify a comma-separated list of directories you wish to follow when
3027 downloading---the same as @samp{-I @var{string}}.
3030 When set to on, enable internationalized URI (IRI) support; the same as
3033 @item inet4_only = on/off
3034 Force connecting to IPv4 addresses, off by default. You can put this
3035 in the global init file to disable Wget's attempts to resolve and
3036 connect to IPv6 hosts. Available only if Wget was compiled with IPv6
3037 support. The same as @samp{--inet4-only} or @samp{-4}.
3039 @item inet6_only = on/off
3040 Force connecting to IPv6 addresses, off by default. Available only if
3041 Wget was compiled with IPv6 support. The same as @samp{--inet6-only}
3044 @item input = @var{file}
3045 Read the @sc{url}s from @var{string}, like @samp{-i @var{file}}.
3047 @item keep_session_cookies = on/off
3048 When specified, causes @samp{save_cookies = on} to also save session
3049 cookies. See @samp{--keep-session-cookies}.
3051 @item limit_rate = @var{rate}
3052 Limit the download speed to no more than @var{rate} bytes per second.
3053 The same as @samp{--limit-rate=@var{rate}}.
3055 @item load_cookies = @var{file}
3056 Load cookies from @var{file}. See @samp{--load-cookies @var{file}}.
3058 @item local_encoding = @var{encoding}
3059 Force Wget to use @var{encoding} as the default system encoding. See
3060 @samp{--local-encoding}.
3062 @item logfile = @var{file}
3063 Set logfile to @var{file}, the same as @samp{-o @var{file}}.
3065 @item max_redirect = @var{number}
3066 Specifies the maximum number of redirections to follow for a resource.
3067 See @samp{--max-redirect=@var{number}}.
3069 @item mirror = on/off
3070 Turn mirroring on/off. The same as @samp{-m}.
3072 @item netrc = on/off
3073 Turn reading netrc on or off.
3075 @item no_clobber = on/off
3078 @item no_parent = on/off
3079 Disallow retrieving outside the directory hierarchy, like
3080 @samp{--no-parent} (@pxref{Directory-Based Limits}).
3082 @item no_proxy = @var{string}
3083 Use @var{string} as the comma-separated list of domains to avoid in
3084 proxy loading, instead of the one specified in environment.
3086 @item output_document = @var{file}
3087 Set the output filename---the same as @samp{-O @var{file}}.
3089 @item page_requisites = on/off
3090 Download all ancillary documents necessary for a single @sc{html} page to
3091 display properly---the same as @samp{-p}.
3093 @item passive_ftp = on/off
3094 Change setting of passive @sc{ftp}, equivalent to the
3095 @samp{--passive-ftp} option.
3097 @itemx password = @var{string}
3098 Specify password @var{string} for both @sc{ftp} and @sc{http} file retrieval.
3099 This command can be overridden using the @samp{ftp_password} and
3100 @samp{http_password} command for @sc{ftp} and @sc{http} respectively.
3102 @item post_data = @var{string}
3103 Use POST as the method for all HTTP requests and send @var{string} in
3104 the request body. The same as @samp{--post-data=@var{string}}.
3106 @item post_file = @var{file}
3107 Use POST as the method for all HTTP requests and send the contents of
3108 @var{file} in the request body. The same as
3109 @samp{--post-file=@var{file}}.
3111 @item prefer_family = none/IPv4/IPv6
3112 When given a choice of several addresses, connect to the addresses
3113 with specified address family first. The address order returned by
3114 DNS is used without change by default. The same as @samp{--prefer-family},
3115 which see for a detailed discussion of why this is useful.
3117 @item private_key = @var{file}
3118 Set the private key file to @var{file}. The same as
3119 @samp{--private-key=@var{file}}.
3121 @item private_key_type = @var{string}
3122 Specify the type of the private key, legal values being @samp{PEM}
3123 (the default) and @samp{DER} (aka ASN1). The same as
3124 @samp{--private-type=@var{string}}.
3126 @item progress = @var{string}
3127 Set the type of the progress indicator. Legal types are @samp{dot}
3128 and @samp{bar}. Equivalent to @samp{--progress=@var{string}}.
3130 @item protocol_directories = on/off
3131 When set, use the protocol name as a directory component of local file
3132 names. The same as @samp{--protocol-directories}.
3134 @item proxy_password = @var{string}
3135 Set proxy authentication password to @var{string}, like
3136 @samp{--proxy-password=@var{string}}.
3138 @item proxy_user = @var{string}
3139 Set proxy authentication user name to @var{string}, like
3140 @samp{--proxy-user=@var{string}}.
3142 @item quiet = on/off
3143 Quiet mode---the same as @samp{-q}.
3145 @item quota = @var{quota}
3146 Specify the download quota, which is useful to put in the global
3147 @file{wgetrc}. When download quota is specified, Wget will stop
3148 retrieving after the download sum has become greater than quota. The
3149 quota can be specified in bytes (default), kbytes @samp{k} appended) or
3150 mbytes (@samp{m} appended). Thus @samp{quota = 5m} will set the quota
3151 to 5 megabytes. Note that the user's startup file overrides system
3154 @item random_file = @var{file}
3155 Use @var{file} as a source of randomness on systems lacking
3158 @item random_wait = on/off
3159 Turn random between-request wait times on or off. The same as
3160 @samp{--random-wait}.
3162 @item read_timeout = @var{n}
3163 Set the read (and write) timeout---the same as
3164 @samp{--read-timeout=@var{n}}.
3166 @item reclevel = @var{n}
3167 Recursion level (depth)---the same as @samp{-l @var{n}}.
3169 @item recursive = on/off
3170 Recursive on/off---the same as @samp{-r}.
3172 @item referer = @var{string}
3173 Set HTTP @samp{Referer:} header just like
3174 @samp{--referer=@var{string}}. (Note that it was the folks who wrote
3175 the @sc{http} spec who got the spelling of ``referrer'' wrong.)
3177 @item relative_only = on/off
3178 Follow only relative links---the same as @samp{-L} (@pxref{Relative
3181 @item remote_encoding = @var{encoding}
3182 Force Wget to use @var{encoding} as the default remote server encoding.
3183 See @samp{--remote-encoding}.
3185 @item remove_listing = on/off
3186 If set to on, remove @sc{ftp} listings downloaded by Wget. Setting it
3187 to off is the same as @samp{--no-remove-listing}.
3189 @item restrict_file_names = unix/windows
3190 Restrict the file names generated by Wget from URLs. See
3191 @samp{--restrict-file-names} for a more detailed description.
3193 @item retr_symlinks = on/off
3194 When set to on, retrieve symbolic links as if they were plain files; the
3195 same as @samp{--retr-symlinks}.
3197 @item retry_connrefused = on/off
3198 When set to on, consider ``connection refused'' a transient
3199 error---the same as @samp{--retry-connrefused}.
3201 @item robots = on/off
3202 Specify whether the norobots convention is respected by Wget, ``on'' by
3203 default. This switch controls both the @file{/robots.txt} and the
3204 @samp{nofollow} aspect of the spec. @xref{Robot Exclusion}, for more
3205 details about this. Be sure you know what you are doing before turning
3208 @item save_cookies = @var{file}
3209 Save cookies to @var{file}. The same as @samp{--save-cookies
3212 @item save_headers = on/off
3213 Same as @samp{--save-headers}.
3215 @item secure_protocol = @var{string}
3216 Choose the secure protocol to be used. Legal values are @samp{auto}
3217 (the default), @samp{SSLv2}, @samp{SSLv3}, and @samp{TLSv1}. The same
3218 as @samp{--secure-protocol=@var{string}}.
3220 @item server_response = on/off
3221 Choose whether or not to print the @sc{http} and @sc{ftp} server
3222 responses---the same as @samp{-S}.
3224 @item show_all_dns_entries = on/off
3225 When a DNS name is resolved, show all the IP addresses, not just the first
3228 @item span_hosts = on/off
3231 @item spider = on/off
3232 Same as @samp{--spider}.
3234 @item strict_comments = on/off
3235 Same as @samp{--strict-comments}.
3237 @item timeout = @var{n}
3238 Set all applicable timeout values to @var{n}, the same as @samp{-T
3241 @item timestamping = on/off
3242 Turn timestamping on/off. The same as @samp{-N} (@pxref{Time-Stamping}).
3244 @item use_server_timestamps = on/off
3245 If set to @samp{off}, Wget won't set the local file's timestamp by the
3246 one on the server (same as @samp{--no-use-server-timestamps}).
3248 @item tries = @var{n}
3249 Set number of retries per @sc{url}---the same as @samp{-t @var{n}}.
3251 @item use_proxy = on/off
3252 When set to off, don't use proxy even when proxy-related environment
3253 variables are set. In that case it is the same as using
3256 @item user = @var{string}
3257 Specify username @var{string} for both @sc{ftp} and @sc{http} file retrieval.
3258 This command can be overridden using the @samp{ftp_user} and
3259 @samp{http_user} command for @sc{ftp} and @sc{http} respectively.
3261 @item user_agent = @var{string}
3262 User agent identification sent to the HTTP Server---the same as
3263 @samp{--user-agent=@var{string}}.
3265 @item verbose = on/off
3266 Turn verbose on/off---the same as @samp{-v}/@samp{-nv}.
3268 @item wait = @var{n}
3269 Wait @var{n} seconds between retrievals---the same as @samp{-w
3272 @item wait_retry = @var{n}
3273 Wait up to @var{n} seconds between retries of failed retrievals
3274 only---the same as @samp{--waitretry=@var{n}}. Note that this is
3275 turned on by default in the global @file{wgetrc}.
3278 @node Sample Wgetrc, , Wgetrc Commands, Startup File
3279 @section Sample Wgetrc
3280 @cindex sample wgetrc
3282 This is the sample initialization file, as given in the distribution.
3283 It is divided in two section---one for global usage (suitable for global
3284 startup file), and one for local usage (suitable for
3285 @file{$HOME/.wgetrc}). Be careful about the things you change.
3287 Note that almost all the lines are commented out. For a command to have
3288 any effect, you must remove the @samp{#} character at the beginning of
3292 @include sample.wgetrc.munged_for_texi_inclusion
3295 @node Examples, Various, Startup File, Top
3299 @c man begin EXAMPLES
3300 The examples are divided into three sections loosely based on their
3304 * Simple Usage:: Simple, basic usage of the program.
3305 * Advanced Usage:: Advanced tips.
3306 * Very Advanced Usage:: The hairy stuff.
3309 @node Simple Usage, Advanced Usage, Examples, Examples
3310 @section Simple Usage
3314 Say you want to download a @sc{url}. Just type:
3317 wget http://fly.srk.fer.hr/
3321 But what will happen if the connection is slow, and the file is lengthy?
3322 The connection will probably fail before the whole file is retrieved,
3323 more than once. In this case, Wget will try getting the file until it
3324 either gets the whole of it, or exceeds the default number of retries
3325 (this being 20). It is easy to change the number of tries to 45, to
3326 insure that the whole file will arrive safely:
3329 wget --tries=45 http://fly.srk.fer.hr/jpg/flyweb.jpg
3333 Now let's leave Wget to work in the background, and write its progress
3334 to log file @file{log}. It is tiring to type @samp{--tries}, so we
3335 shall use @samp{-t}.
3338 wget -t 45 -o log http://fly.srk.fer.hr/jpg/flyweb.jpg &
3341 The ampersand at the end of the line makes sure that Wget works in the
3342 background. To unlimit the number of retries, use @samp{-t inf}.
3345 The usage of @sc{ftp} is as simple. Wget will take care of login and
3349 wget ftp://gnjilux.srk.fer.hr/welcome.msg
3353 If you specify a directory, Wget will retrieve the directory listing,
3354 parse it and convert it to @sc{html}. Try:
3357 wget ftp://ftp.gnu.org/pub/gnu/
3362 @node Advanced Usage, Very Advanced Usage, Simple Usage, Examples
3363 @section Advanced Usage
3367 You have a file that contains the URLs you want to download? Use the
3374 If you specify @samp{-} as file name, the @sc{url}s will be read from
3378 Create a five levels deep mirror image of the GNU web site, with the
3379 same directory structure the original has, with only one try per
3380 document, saving the log of the activities to @file{gnulog}:
3383 wget -r http://www.gnu.org/ -o gnulog
3387 The same as the above, but convert the links in the downloaded files to
3388 point to local files, so you can view the documents off-line:
3391 wget --convert-links -r http://www.gnu.org/ -o gnulog
3395 Retrieve only one @sc{html} page, but make sure that all the elements needed
3396 for the page to be displayed, such as inline images and external style
3397 sheets, are also downloaded. Also make sure the downloaded page
3398 references the downloaded links.
3401 wget -p --convert-links http://www.server.com/dir/page.html
3404 The @sc{html} page will be saved to @file{www.server.com/dir/page.html}, and
3405 the images, stylesheets, etc., somewhere under @file{www.server.com/},
3406 depending on where they were on the remote server.
3409 The same as the above, but without the @file{www.server.com/} directory.
3410 In fact, I don't want to have all those random server directories
3411 anyway---just save @emph{all} those files under a @file{download/}
3412 subdirectory of the current directory.
3415 wget -p --convert-links -nH -nd -Pdownload \
3416 http://www.server.com/dir/page.html
3420 Retrieve the index.html of @samp{www.lycos.com}, showing the original
3424 wget -S http://www.lycos.com/
3428 Save the server headers with the file, perhaps for post-processing.
3431 wget --save-headers http://www.lycos.com/
3436 Retrieve the first two levels of @samp{wuarchive.wustl.edu}, saving them
3440 wget -r -l2 -P/tmp ftp://wuarchive.wustl.edu/
3444 You want to download all the @sc{gif}s from a directory on an @sc{http}
3445 server. You tried @samp{wget http://www.server.com/dir/*.gif}, but that
3446 didn't work because @sc{http} retrieval does not support globbing. In
3450 wget -r -l1 --no-parent -A.gif http://www.server.com/dir/
3453 More verbose, but the effect is the same. @samp{-r -l1} means to
3454 retrieve recursively (@pxref{Recursive Download}), with maximum depth
3455 of 1. @samp{--no-parent} means that references to the parent directory
3456 are ignored (@pxref{Directory-Based Limits}), and @samp{-A.gif} means to
3457 download only the @sc{gif} files. @samp{-A "*.gif"} would have worked
3461 Suppose you were in the middle of downloading, when Wget was
3462 interrupted. Now you do not want to clobber the files already present.
3466 wget -nc -r http://www.gnu.org/
3470 If you want to encode your own username and password to @sc{http} or
3471 @sc{ftp}, use the appropriate @sc{url} syntax (@pxref{URL Format}).
3474 wget ftp://hniksic:mypassword@@unix.server.com/.emacs
3477 Note, however, that this usage is not advisable on multi-user systems
3478 because it reveals your password to anyone who looks at the output of
3481 @cindex redirecting output
3483 You would like the output documents to go to standard output instead of
3487 wget -O - http://jagor.srce.hr/ http://www.srce.hr/
3490 You can also combine the two options and make pipelines to retrieve the
3491 documents from remote hotlists:
3494 wget -O - http://cool.list.com/ | wget --force-html -i -
3498 @node Very Advanced Usage, , Advanced Usage, Examples
3499 @section Very Advanced Usage
3504 If you wish Wget to keep a mirror of a page (or @sc{ftp}
3505 subdirectories), use @samp{--mirror} (@samp{-m}), which is the shorthand
3506 for @samp{-r -l inf -N}. You can put Wget in the crontab file asking it
3507 to recheck a site each Sunday:
3511 0 0 * * 0 wget --mirror http://www.gnu.org/ -o /home/me/weeklog
3515 In addition to the above, you want the links to be converted for local
3516 viewing. But, after having read this manual, you know that link
3517 conversion doesn't play well with timestamping, so you also want Wget to
3518 back up the original @sc{html} files before the conversion. Wget invocation
3519 would look like this:
3522 wget --mirror --convert-links --backup-converted \
3523 http://www.gnu.org/ -o /home/me/weeklog
3527 But you've also noticed that local viewing doesn't work all that well
3528 when @sc{html} files are saved under extensions other than @samp{.html},
3529 perhaps because they were served as @file{index.cgi}. So you'd like
3530 Wget to rename all the files served with content-type @samp{text/html}
3531 or @samp{application/xhtml+xml} to @file{@var{name}.html}.
3534 wget --mirror --convert-links --backup-converted \
3535 --html-extension -o /home/me/weeklog \
3539 Or, with less typing:
3542 wget -m -k -K -E http://www.gnu.org/ -o /home/me/weeklog
3547 @node Various, Appendices, Examples, Top
3551 This chapter contains all the stuff that could not fit anywhere else.
3554 * Proxies:: Support for proxy servers.
3555 * Distribution:: Getting the latest version.
3556 * Web Site:: GNU Wget's presence on the World Wide Web.
3557 * Mailing Lists:: Wget mailing list for announcements and discussion.
3558 * Internet Relay Chat:: Wget's presence on IRC.
3559 * Reporting Bugs:: How and where to report bugs.
3560 * Portability:: The systems Wget works on.
3561 * Signals:: Signal-handling performed by Wget.
3564 @node Proxies, Distribution, Various, Various
3568 @dfn{Proxies} are special-purpose @sc{http} servers designed to transfer
3569 data from remote servers to local clients. One typical use of proxies
3570 is lightening network load for users behind a slow connection. This is
3571 achieved by channeling all @sc{http} and @sc{ftp} requests through the
3572 proxy which caches the transferred data. When a cached resource is
3573 requested again, proxy will return the data from cache. Another use for
3574 proxies is for companies that separate (for security reasons) their
3575 internal networks from the rest of Internet. In order to obtain
3576 information from the Web, their users connect and retrieve remote data
3577 using an authorized proxy.
3579 Wget supports proxies for both @sc{http} and @sc{ftp} retrievals. The
3580 standard way to specify proxy location, which Wget recognizes, is using
3581 the following environment variables:
3586 If set, the @code{http_proxy} and @code{https_proxy} variables should
3587 contain the @sc{url}s of the proxies for @sc{http} and @sc{https}
3588 connections respectively.
3591 This variable should contain the @sc{url} of the proxy for @sc{ftp}
3592 connections. It is quite common that @code{http_proxy} and
3593 @code{ftp_proxy} are set to the same @sc{url}.
3596 This variable should contain a comma-separated list of domain extensions
3597 proxy should @emph{not} be used for. For instance, if the value of
3598 @code{no_proxy} is @samp{.mit.edu}, proxy will not be used to retrieve
3602 In addition to the environment variables, proxy location and settings
3603 may be specified from within Wget itself.
3607 @itemx proxy = on/off
3608 This option and the corresponding command may be used to suppress the
3609 use of proxy, even if the appropriate environment variables are set.
3611 @item http_proxy = @var{URL}
3612 @itemx https_proxy = @var{URL}
3613 @itemx ftp_proxy = @var{URL}
3614 @itemx no_proxy = @var{string}
3615 These startup file variables allow you to override the proxy settings
3616 specified by the environment.
3619 Some proxy servers require authorization to enable you to use them. The
3620 authorization consists of @dfn{username} and @dfn{password}, which must
3621 be sent by Wget. As with @sc{http} authorization, several
3622 authentication schemes exist. For proxy authorization only the
3623 @code{Basic} authentication scheme is currently implemented.
3625 You may specify your username and password either through the proxy
3626 @sc{url} or through the command-line options. Assuming that the
3627 company's proxy is located at @samp{proxy.company.com} at port 8001, a
3628 proxy @sc{url} location containing authorization data might look like
3632 http://hniksic:mypassword@@proxy.company.com:8001/
3635 Alternatively, you may use the @samp{proxy-user} and
3636 @samp{proxy-password} options, and the equivalent @file{.wgetrc}
3637 settings @code{proxy_user} and @code{proxy_password} to set the proxy
3638 username and password.
3640 @node Distribution, Web Site, Proxies, Various
3641 @section Distribution
3642 @cindex latest version
3644 Like all GNU utilities, the latest version of Wget can be found at the
3645 master GNU archive site ftp.gnu.org, and its mirrors. For example,
3646 Wget @value{VERSION} can be found at
3647 @url{ftp://ftp.gnu.org/pub/gnu/wget/wget-@value{VERSION}.tar.gz}
3649 @node Web Site, Mailing Lists, Distribution, Various
3653 The official web site for GNU Wget is at
3654 @url{http://www.gnu.org/software/wget/}. However, most useful
3655 information resides at ``The Wget Wgiki'',
3656 @url{http://wget.addictivecode.org/}.
3658 @node Mailing Lists, Internet Relay Chat, Web Site, Various
3659 @section Mailing Lists
3660 @cindex mailing list
3663 @unnumberedsubsec Primary List
3665 The primary mailinglist for discussion, bug-reports, or questions
3666 about GNU Wget is at @email{bug-wget@@gnu.org}. To subscribe, send an
3667 email to @email{bug-wget-join@@gnu.org}, or visit
3668 @url{http://lists.gnu.org/mailman/listinfo/bug-wget}.
3670 You do not need to subscribe to send a message to the list; however,
3671 please note that unsubscribed messages are moderated, and may take a
3672 while before they hit the list---@strong{usually around a day}. If
3673 you want your message to show up immediately, please subscribe to the
3674 list before posting. Archives for the list may be found at
3675 @url{http://lists.gnu.org/pipermail/bug-wget/}.
3677 An NNTP/Usenettish gateway is also available via
3678 @uref{http://gmane.org/about.php,Gmane}. You can see the Gmane
3680 @url{http://news.gmane.org/gmane.comp.web.wget.general}. Note that the
3681 Gmane archives conveniently include messages from both the current
3682 list, and the previous one. Messages also show up in the Gmane
3683 archives sooner than they do at @url{lists.gnu.org}.
3685 @unnumberedsubsec Bug Notices List
3687 Additionally, there is the @email{wget-notify@@addictivecode.org} mailing
3688 list. This is a non-discussion list that receives bug report
3689 notifications from the bug-tracker. To subscribe to this list,
3690 send an email to @email{wget-notify-join@@addictivecode.org},
3691 or visit @url{http://addictivecode.org/mailman/listinfo/wget-notify}.
3693 @unnumberedsubsec Obsolete Lists
3695 Previously, the mailing list @email{wget@@sunsite.dk} was used as the
3696 main discussion list, and another list,
3697 @email{wget-patches@@sunsite.dk} was used for submitting and
3698 discussing patches to GNU Wget.
3700 Messages from @email{wget@@sunsite.dk} are archived at
3703 @url{http://www.mail-archive.com/wget%40sunsite.dk/} and at
3705 @url{http://news.gmane.org/gmane.comp.web.wget.general} (which also
3706 continues to archive the current list, @email{bug-wget@@gnu.org}).
3709 Messages from @email{wget-patches@@sunsite.dk} are archived at
3712 @url{http://news.gmane.org/gmane.comp.web.wget.patches}.
3715 @node Internet Relay Chat, Reporting Bugs, Mailing Lists, Various
3716 @section Internet Relay Chat
3717 @cindex Internet Relay Chat
3721 In addition to the mailinglists, we also have a support channel set up
3722 via IRC at @code{irc.freenode.org}, @code{#wget}. Come check it out!
3724 @node Reporting Bugs, Portability, Internet Relay Chat, Various
3725 @section Reporting Bugs
3727 @cindex reporting bugs
3731 You are welcome to submit bug reports via the GNU Wget bug tracker (see
3732 @url{http://wget.addictivecode.org/BugTracker}).
3734 Before actually submitting a bug report, please try to follow a few
3739 Please try to ascertain that the behavior you see really is a bug. If
3740 Wget crashes, it's a bug. If Wget does not behave as documented,
3741 it's a bug. If things work strange, but you are not sure about the way
3742 they are supposed to work, it might well be a bug, but you might want to
3743 double-check the documentation and the mailing lists (@pxref{Mailing
3747 Try to repeat the bug in as simple circumstances as possible. E.g. if
3748 Wget crashes while downloading @samp{wget -rl0 -kKE -t5 --no-proxy
3749 http://yoyodyne.com -o /tmp/log}, you should try to see if the crash is
3750 repeatable, and if will occur with a simpler set of options. You might
3751 even try to start the download at the page where the crash occurred to
3752 see if that page somehow triggered the crash.
3754 Also, while I will probably be interested to know the contents of your
3755 @file{.wgetrc} file, just dumping it into the debug message is probably
3756 a bad idea. Instead, you should first try to see if the bug repeats
3757 with @file{.wgetrc} moved out of the way. Only if it turns out that
3758 @file{.wgetrc} settings affect the bug, mail me the relevant parts of
3762 Please start Wget with @samp{-d} option and send us the resulting
3763 output (or relevant parts thereof). If Wget was compiled without
3764 debug support, recompile it---it is @emph{much} easier to trace bugs
3765 with debug support on.
3767 Note: please make sure to remove any potentially sensitive information
3768 from the debug log before sending it to the bug address. The
3769 @code{-d} won't go out of its way to collect sensitive information,
3770 but the log @emph{will} contain a fairly complete transcript of Wget's
3771 communication with the server, which may include passwords and pieces
3772 of downloaded data. Since the bug address is publically archived, you
3773 may assume that all bug reports are visible to the public.
3776 If Wget has crashed, try to run it in a debugger, e.g. @code{gdb `which
3777 wget` core} and type @code{where} to get the backtrace. This may not
3778 work if the system administrator has disabled core files, but it is
3783 @node Portability, Signals, Reporting Bugs, Various
3784 @section Portability
3786 @cindex operating systems
3788 Like all GNU software, Wget works on the GNU system. However, since it
3789 uses GNU Autoconf for building and configuring, and mostly avoids using
3790 ``special'' features of any particular Unix, it should compile (and
3791 work) on all common Unix flavors.
3793 Various Wget versions have been compiled and tested under many kinds of
3794 Unix systems, including GNU/Linux, Solaris, SunOS 4.x, Mac OS X, OSF
3795 (aka Digital Unix or Tru64), Ultrix, *BSD, IRIX, AIX, and others. Some
3796 of those systems are no longer in widespread use and may not be able to
3797 support recent versions of Wget. If Wget fails to compile on your
3798 system, we would like to know about it.
3800 Thanks to kind contributors, this version of Wget compiles and works
3801 on 32-bit Microsoft Windows platforms. It has been compiled
3802 successfully using MS Visual C++ 6.0, Watcom, Borland C, and GCC
3803 compilers. Naturally, it is crippled of some features available on
3804 Unix, but it should work as a substitute for people stuck with
3805 Windows. Note that Windows-specific portions of Wget are not
3806 guaranteed to be supported in the future, although this has been the
3807 case in practice for many years now. All questions and problems in
3808 Windows usage should be reported to Wget mailing list at
3809 @email{wget@@sunsite.dk} where the volunteers who maintain the
3810 Windows-related features might look at them.
3812 Support for building on MS-DOS via DJGPP has been contributed by Gisle
3813 Vanem; a port to VMS is maintained by Steven Schweda, and is available
3814 at @url{http://antinode.org/}.
3816 @node Signals, , Portability, Various
3818 @cindex signal handling
3821 Since the purpose of Wget is background work, it catches the hangup
3822 signal (@code{SIGHUP}) and ignores it. If the output was on standard
3823 output, it will be redirected to a file named @file{wget-log}.
3824 Otherwise, @code{SIGHUP} is ignored. This is convenient when you wish
3825 to redirect the output of Wget after having started it.
3828 $ wget http://www.gnus.org/dist/gnus.tar.gz &
3831 SIGHUP received, redirecting output to `wget-log'.
3834 Other than that, Wget will not try to interfere with signals in any way.
3835 @kbd{C-c}, @code{kill -TERM} and @code{kill -KILL} should kill it alike.
3837 @node Appendices, Copying this manual, Various, Top
3840 This chapter contains some references I consider useful.
3843 * Robot Exclusion:: Wget's support for RES.
3844 * Security Considerations:: Security with Wget.
3845 * Contributors:: People who helped.
3848 @node Robot Exclusion, Security Considerations, Appendices, Appendices
3849 @section Robot Exclusion
3850 @cindex robot exclusion
3852 @cindex server maintenance
3854 It is extremely easy to make Wget wander aimlessly around a web site,
3855 sucking all the available data in progress. @samp{wget -r @var{site}},
3856 and you're set. Great? Not for the server admin.
3858 As long as Wget is only retrieving static pages, and doing it at a
3859 reasonable rate (see the @samp{--wait} option), there's not much of a
3860 problem. The trouble is that Wget can't tell the difference between the
3861 smallest static page and the most demanding CGI. A site I know has a
3862 section handled by a CGI Perl script that converts Info files to @sc{html} on
3863 the fly. The script is slow, but works well enough for human users
3864 viewing an occasional Info file. However, when someone's recursive Wget
3865 download stumbles upon the index page that links to all the Info files
3866 through the script, the system is brought to its knees without providing
3867 anything useful to the user (This task of converting Info files could be
3868 done locally and access to Info documentation for all installed GNU
3869 software on a system is available from the @code{info} command).
3871 To avoid this kind of accident, as well as to preserve privacy for
3872 documents that need to be protected from well-behaved robots, the
3873 concept of @dfn{robot exclusion} was invented. The idea is that
3874 the server administrators and document authors can specify which
3875 portions of the site they wish to protect from robots and those
3876 they will permit access.
3878 The most popular mechanism, and the @i{de facto} standard supported by
3879 all the major robots, is the ``Robots Exclusion Standard'' (RES) written
3880 by Martijn Koster et al. in 1994. It specifies the format of a text
3881 file containing directives that instruct the robots which URL paths to
3882 avoid. To be found by the robots, the specifications must be placed in
3883 @file{/robots.txt} in the server root, which the robots are expected to
3886 Although Wget is not a web robot in the strictest sense of the word, it
3887 can download large parts of the site without the user's intervention to
3888 download an individual page. Because of that, Wget honors RES when
3889 downloading recursively. For instance, when you issue:
3892 wget -r http://www.server.com/
3895 First the index of @samp{www.server.com} will be downloaded. If Wget
3896 finds that it wants to download more documents from that server, it will
3897 request @samp{http://www.server.com/robots.txt} and, if found, use it
3898 for further downloads. @file{robots.txt} is loaded only once per each
3901 Until version 1.8, Wget supported the first version of the standard,
3902 written by Martijn Koster in 1994 and available at
3903 @url{http://www.robotstxt.org/wc/norobots.html}. As of version 1.8,
3904 Wget has supported the additional directives specified in the internet
3905 draft @samp{<draft-koster-robots-00.txt>} titled ``A Method for Web
3906 Robots Control''. The draft, which has as far as I know never made to
3907 an @sc{rfc}, is available at
3908 @url{http://www.robotstxt.org/wc/norobots-rfc.txt}.
3910 This manual no longer includes the text of the Robot Exclusion Standard.
3912 The second, less known mechanism, enables the author of an individual
3913 document to specify whether they want the links from the file to be
3914 followed by a robot. This is achieved using the @code{META} tag, like
3918 <meta name="robots" content="nofollow">
3921 This is explained in some detail at
3922 @url{http://www.robotstxt.org/wc/meta-user.html}. Wget supports this
3923 method of robot exclusion in addition to the usual @file{/robots.txt}
3926 If you know what you are doing and really really wish to turn off the
3927 robot exclusion, set the @code{robots} variable to @samp{off} in your
3928 @file{.wgetrc}. You can achieve the same effect from the command line
3929 using the @code{-e} switch, e.g. @samp{wget -e robots=off @var{url}...}.
3931 @node Security Considerations, Contributors, Robot Exclusion, Appendices
3932 @section Security Considerations
3935 When using Wget, you must be aware that it sends unencrypted passwords
3936 through the network, which may present a security problem. Here are the
3937 main issues, and some solutions.
3941 The passwords on the command line are visible using @code{ps}. The best
3942 way around it is to use @code{wget -i -} and feed the @sc{url}s to
3943 Wget's standard input, each on a separate line, terminated by @kbd{C-d}.
3944 Another workaround is to use @file{.netrc} to store passwords; however,
3945 storing unencrypted passwords is also considered a security risk.
3948 Using the insecure @dfn{basic} authentication scheme, unencrypted
3949 passwords are transmitted through the network routers and gateways.
3952 The @sc{ftp} passwords are also in no way encrypted. There is no good
3953 solution for this at the moment.
3956 Although the ``normal'' output of Wget tries to hide the passwords,
3957 debugging logs show them, in all forms. This problem is avoided by
3958 being careful when you send debug logs (yes, even when you send them to
3962 @node Contributors, , Security Considerations, Appendices
3963 @section Contributors
3964 @cindex contributors
3967 GNU Wget was written by Hrvoje Nik@v{s}i@'{c} @email{hniksic@@xemacs.org},
3970 GNU Wget was written by Hrvoje Niksic @email{hniksic@@xemacs.org}.
3973 However, the development of Wget could never have gone as far as it has, were
3974 it not for the help of many people, either with bug reports, feature proposals,
3975 patches, or letters saying ``Thanks!''.
3977 Special thanks goes to the following people (no particular order):
3980 @item Dan Harkless---contributed a lot of code and documentation of
3981 extremely high quality, as well as the @code{--page-requisites} and
3982 related options. He was the principal maintainer for some time and
3985 @item Ian Abbott---contributed bug fixes, Windows-related fixes, and
3986 provided a prototype implementation of the breadth-first recursive
3987 download. Co-maintained Wget during the 1.8 release cycle.
3990 The dotsrc.org crew, in particular Karsten Thygesen---donated system
3991 resources such as the mailing list, web space, @sc{ftp} space, and
3992 version control repositories, along with a lot of time to make these
3993 actually work. Christian Reiniger was of invaluable help with setting
3997 Heiko Herold---provided high-quality Windows builds and contributed
3998 bug and build reports for many years.
4001 Shawn McHorse---bug reports and patches.
4004 Kaveh R. Ghazi---on-the-fly @code{ansi2knr}-ization. Lots of
4008 Gordon Matzigkeit---@file{.netrc} support.
4012 Zlatko @v{C}alu@v{s}i@'{c}, Tomislav Vujec and Dra@v{z}en
4013 Ka@v{c}ar---feature suggestions and ``philosophical'' discussions.
4016 Zlatko Calusic, Tomislav Vujec and Drazen Kacar---feature suggestions
4017 and ``philosophical'' discussions.
4021 Darko Budor---initial port to Windows.
4024 Antonio Rosella---help and suggestions, plus the initial Italian
4029 Tomislav Petrovi@'{c}, Mario Miko@v{c}evi@'{c}---many bug reports and
4033 Tomislav Petrovic, Mario Mikocevic---many bug reports and suggestions.
4038 Fran@,{c}ois Pinard---many thorough bug reports and discussions.
4041 Francois Pinard---many thorough bug reports and discussions.
4045 Karl Eichwalder---lots of help with internationalization, Makefile
4046 layout and many other things.
4049 Junio Hamano---donated support for Opie and @sc{http} @code{Digest}
4053 Mauro Tortonesi---improved IPv6 support, adding support for dual
4054 family systems. Refactored and enhanced FTP IPv6 code. Maintained GNU
4055 Wget from 2004--2007.
4058 Christopher G.@: Lewis---maintenance of the Windows version of GNU WGet.
4061 Gisle Vanem---many helpful patches and improvements, especially for
4062 Windows and MS-DOS support.
4065 Ralf Wildenhues---contributed patches to convert Wget to use Automake as
4066 part of its build process, and various bugfixes.
4069 Steven Schubiger---Many helpful patches, bugfixes and improvements.
4070 Notably, conversion of Wget to use the Gnulib quotes and quoteargs
4071 modules, and the addition of password prompts at the console, via the
4072 Gnulib getpasswd-gnu module.
4075 Ted Mielczarek---donated support for CSS.
4078 Saint Xavier---Support for IRIs (RFC 3987).
4081 People who provided donations for development---including Brian Gough.
4084 The following people have provided patches, bug/build reports, useful
4085 suggestions, beta testing services, fan mail and all the other things
4086 that make maintenance so much fun:
4106 Kristijan @v{C}onka@v{s},
4115 Bertrand Demiddelaer,
4116 Alexander Dergachev,
4129 Aleksandar Erkalovi@'{c},
4132 Aleksandar Erkalovic,
4156 Madhusudan Hosaagrahara,
4160 Erik Magnus Hulthen,
4179 Goran Kezunovi@'{c},
4193 $\Sigma\acute{\iota}\mu o\varsigma\;
4194 \Xi\varepsilon\nu\iota\tau\acute{\epsilon}\lambda\lambda\eta\varsigma$
4195 (Simos KSenitellis),
4204 Nicol@'{a}s Lichtmeier,
4210 Alexander V.@: Lukyanov,
4219 Matthew J.@: Mellon,
4255 @c Texinfo doesn't grok @'{@i}, so we have to use TeX itself.
4257 Juan Jos\'{e} Rodr\'{\i}guez,
4260 Juan Jose Rodriguez,
4262 Maciej W.@: Rozycki,
4269 Steven M.@: Schweda,
4280 Szakacsits Szabolcs,
4295 Douglas E.@: Wegscheid,
4297 Joshua David Williams,
4311 Apologies to all who I accidentally left out, and many thanks to all the
4312 subscribers of the Wget mailing list.
4314 @node Copying this manual, Concept Index, Appendices, Top
4315 @appendix Copying this manual
4318 * GNU Free Documentation License:: Licnse for copying this manual.
4321 @node GNU Free Documentation License, , Copying this manual, Copying this manual
4322 @appendixsec GNU Free Documentation License
4323 @cindex FDL, GNU Free Documentation License
4328 @node Concept Index, , Copying this manual, Top
4329 @unnumbered Concept Index