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
482 @item --report-speed=@var{type}
483 Output bandwidth as @var{type}. The only accepted value is @samp{bits}.
487 @itemx --input-file=@var{file}
488 Read @sc{url}s from a local or external @var{file}. If @samp{-} is
489 specified as @var{file}, @sc{url}s are read from the standard input.
490 (Use @samp{./-} to read from a file literally named @samp{-}.)
492 If this function is used, no @sc{url}s need be present on the command
493 line. If there are @sc{url}s both on the command line and in an input
494 file, those on the command lines will be the first ones to be
495 retrieved. If @samp{--force-html} is not specified, then @var{file}
496 should consist of a series of URLs, one per line.
498 However, if you specify @samp{--force-html}, the document will be
499 regarded as @samp{html}. In that case you may have problems with
500 relative links, which you can solve either by adding @code{<base
501 href="@var{url}">} to the documents or by specifying
502 @samp{--base=@var{url}} on the command line.
504 If the @var{file} is an external one, the document will be automatically
505 treated as @samp{html} if the Content-Type matches @samp{text/html}.
506 Furthermore, the @var{file}'s location will be implicitly used as base
507 href if none was specified.
512 When input is read from a file, force it to be treated as an @sc{html}
513 file. This enables you to retrieve relative links from existing
514 @sc{html} files on your local disk, by adding @code{<base
515 href="@var{url}">} to @sc{html}, or using the @samp{--base} command-line
518 @cindex base for relative links in input file
520 @itemx --base=@var{URL}
521 Resolves relative links using @var{URL} as the point of reference,
522 when reading links from an HTML file specified via the
523 @samp{-i}/@samp{--input-file} option (together with
524 @samp{--force-html}, or when the input file was fetched remotely from
525 a server describing it as @sc{html}). This is equivalent to the
526 presence of a @code{BASE} tag in the @sc{html} input file, with
527 @var{URL} as the value for the @code{href} attribute.
529 For instance, if you specify @samp{http://foo/bar/a.html} for
530 @var{URL}, and Wget reads @samp{../baz/b.html} from the input file, it
531 would be resolved to @samp{http://foo/baz/b.html}.
533 @cindex specify config
534 @item --config=@var{FILE}
535 Specify the location of a startup file you wish to use.
538 @node Download Options, Directory Options, Logging and Input File Options, Invoking
539 @section Download Options
543 @cindex client IP address
544 @cindex IP address, client
545 @item --bind-address=@var{ADDRESS}
546 When making client TCP/IP connections, bind to @var{ADDRESS} on
547 the local machine. @var{ADDRESS} may be specified as a hostname or IP
548 address. This option can be useful if your machine is bound to multiple
553 @cindex number of retries
554 @item -t @var{number}
555 @itemx --tries=@var{number}
556 Set number of retries to @var{number}. Specify 0 or @samp{inf} for
557 infinite retrying. The default is to retry 20 times, with the exception
558 of fatal errors like ``connection refused'' or ``not found'' (404),
559 which are not retried.
562 @itemx --output-document=@var{file}
563 The documents will not be written to the appropriate files, but all
564 will be concatenated together and written to @var{file}. If @samp{-}
565 is used as @var{file}, documents will be printed to standard output,
566 disabling link conversion. (Use @samp{./-} to print to a file
567 literally named @samp{-}.)
569 Use of @samp{-O} is @emph{not} intended to mean simply ``use the name
570 @var{file} instead of the one in the URL;'' rather, it is
571 analogous to shell redirection:
572 @samp{wget -O file http://foo} is intended to work like
573 @samp{wget -O - http://foo > file}; @file{file} will be truncated
574 immediately, and @emph{all} downloaded content will be written there.
576 For this reason, @samp{-N} (for timestamp-checking) is not supported
577 in combination with @samp{-O}: since @var{file} is always newly
578 created, it will always have a very new timestamp. A warning will be
579 issued if this combination is used.
581 Similarly, using @samp{-r} or @samp{-p} with @samp{-O} may not work as
582 you expect: Wget won't just download the first file to @var{file} and
583 then download the rest to their normal names: @emph{all} downloaded
584 content will be placed in @var{file}. This was disabled in version
585 1.11, but has been reinstated (with a warning) in 1.11.2, as there are
586 some cases where this behavior can actually have some use.
588 Note that a combination with @samp{-k} is only permitted when
589 downloading a single document, as in that case it will just convert
590 all relative URIs to external ones; @samp{-k} makes no sense for
591 multiple URIs when they're all being downloaded to a single file;
592 @samp{-k} can be used only when the output is a regular file.
594 @cindex clobbering, file
595 @cindex downloading multiple times
599 If a file is downloaded more than once in the same directory, Wget's
600 behavior depends on a few options, including @samp{-nc}. In certain
601 cases, the local file will be @dfn{clobbered}, or overwritten, upon
602 repeated download. In other cases it will be preserved.
604 When running Wget without @samp{-N}, @samp{-nc}, @samp{-r}, or
605 @samp{-p}, downloading the same file in the same directory will result
606 in the original copy of @var{file} being preserved and the second copy
607 being named @samp{@var{file}.1}. If that file is downloaded yet
608 again, the third copy will be named @samp{@var{file}.2}, and so on.
609 (This is also the behavior with @samp{-nd}, even if @samp{-r} or
610 @samp{-p} are in effect.) When @samp{-nc} is specified, this behavior
611 is suppressed, and Wget will refuse to download newer copies of
612 @samp{@var{file}}. Therefore, ``@code{no-clobber}'' is actually a
613 misnomer in this mode---it's not clobbering that's prevented (as the
614 numeric suffixes were already preventing clobbering), but rather the
615 multiple version saving that's prevented.
617 When running Wget with @samp{-r} or @samp{-p}, but without @samp{-N},
618 @samp{-nd}, or @samp{-nc}, re-downloading a file will result in the
619 new copy simply overwriting the old. Adding @samp{-nc} will prevent
620 this behavior, instead causing the original version to be preserved
621 and any newer copies on the server to be ignored.
623 When running Wget with @samp{-N}, with or without @samp{-r} or
624 @samp{-p}, the decision as to whether or not to download a newer copy
625 of a file depends on the local and remote timestamp and size of the
626 file (@pxref{Time-Stamping}). @samp{-nc} may not be specified at the
627 same time as @samp{-N}.
629 Note that when @samp{-nc} is specified, files with the suffixes
630 @samp{.html} or @samp{.htm} will be loaded from the local disk and
631 parsed as if they had been retrieved from the Web.
633 @cindex continue retrieval
634 @cindex incomplete downloads
635 @cindex resume download
638 Continue getting a partially-downloaded file. This is useful when you
639 want to finish up a download started by a previous instance of Wget, or
640 by another program. For instance:
643 wget -c ftp://sunsite.doc.ic.ac.uk/ls-lR.Z
646 If there is a file named @file{ls-lR.Z} in the current directory, Wget
647 will assume that it is the first portion of the remote file, and will
648 ask the server to continue the retrieval from an offset equal to the
649 length of the local file.
651 Note that you don't need to specify this option if you just want the
652 current invocation of Wget to retry downloading a file should the
653 connection be lost midway through. This is the default behavior.
654 @samp{-c} only affects resumption of downloads started @emph{prior} to
655 this invocation of Wget, and whose local files are still sitting around.
657 Without @samp{-c}, the previous example would just download the remote
658 file to @file{ls-lR.Z.1}, leaving the truncated @file{ls-lR.Z} file
661 Beginning with Wget 1.7, if you use @samp{-c} on a non-empty file, and
662 it turns out that the server does not support continued downloading,
663 Wget will refuse to start the download from scratch, which would
664 effectively ruin existing contents. If you really want the download to
665 start from scratch, remove the file.
667 Also beginning with Wget 1.7, if you use @samp{-c} on a file which is of
668 equal size as the one on the server, Wget will refuse to download the
669 file and print an explanatory message. The same happens when the file
670 is smaller on the server than locally (presumably because it was changed
671 on the server since your last download attempt)---because ``continuing''
672 is not meaningful, no download occurs.
674 On the other side of the coin, while using @samp{-c}, any file that's
675 bigger on the server than locally will be considered an incomplete
676 download and only @code{(length(remote) - length(local))} bytes will be
677 downloaded and tacked onto the end of the local file. This behavior can
678 be desirable in certain cases---for instance, you can use @samp{wget -c}
679 to download just the new portion that's been appended to a data
680 collection or log file.
682 However, if the file is bigger on the server because it's been
683 @emph{changed}, as opposed to just @emph{appended} to, you'll end up
684 with a garbled file. Wget has no way of verifying that the local file
685 is really a valid prefix of the remote file. You need to be especially
686 careful of this when using @samp{-c} in conjunction with @samp{-r},
687 since every file will be considered as an "incomplete download" candidate.
689 Another instance where you'll get a garbled file if you try to use
690 @samp{-c} is if you have a lame @sc{http} proxy that inserts a
691 ``transfer interrupted'' string into the local file. In the future a
692 ``rollback'' option may be added to deal with this case.
694 Note that @samp{-c} only works with @sc{ftp} servers and with @sc{http}
695 servers that support the @code{Range} header.
697 @cindex progress indicator
699 @item --progress=@var{type}
700 Select the type of the progress indicator you wish to use. Legal
701 indicators are ``dot'' and ``bar''.
703 The ``bar'' indicator is used by default. It draws an @sc{ascii} progress
704 bar graphics (a.k.a ``thermometer'' display) indicating the status of
705 retrieval. If the output is not a TTY, the ``dot'' bar will be used by
708 Use @samp{--progress=dot} to switch to the ``dot'' display. It traces
709 the retrieval by printing dots on the screen, each dot representing a
710 fixed amount of downloaded data.
712 When using the dotted retrieval, you may also set the @dfn{style} by
713 specifying the type as @samp{dot:@var{style}}. Different styles assign
714 different meaning to one dot. With the @code{default} style each dot
715 represents 1K, there are ten dots in a cluster and 50 dots in a line.
716 The @code{binary} style has a more ``computer''-like orientation---8K
717 dots, 16-dots clusters and 48 dots per line (which makes for 384K
718 lines). The @code{mega} style is suitable for downloading very large
719 files---each dot represents 64K retrieved, there are eight dots in a
720 cluster, and 48 dots on each line (so each line contains 3M).
722 Note that you can set the default style using the @code{progress}
723 command in @file{.wgetrc}. That setting may be overridden from the
724 command line. The exception is that, when the output is not a TTY, the
725 ``dot'' progress will be favored over ``bar''. To force the bar output,
726 use @samp{--progress=bar:force}.
729 @itemx --timestamping
730 Turn on time-stamping. @xref{Time-Stamping}, for details.
732 @item --no-use-server-timestamps
733 Don't set the local file's timestamp by the one on the server.
735 By default, when a file is downloaded, it's timestamps are set to
736 match those from the remote file. This allows the use of
737 @samp{--timestamping} on subsequent invocations of wget. However, it
738 is sometimes useful to base the local file's timestamp on when it was
739 actually downloaded; for that purpose, the
740 @samp{--no-use-server-timestamps} option has been provided.
742 @cindex server response, print
744 @itemx --server-response
745 Print the headers sent by @sc{http} servers and responses sent by
748 @cindex Wget as spider
751 When invoked with this option, Wget will behave as a Web @dfn{spider},
752 which means that it will not download the pages, just check that they
753 are there. For example, you can use Wget to check your bookmarks:
756 wget --spider --force-html -i bookmarks.html
759 This feature needs much more work for Wget to get close to the
760 functionality of real web spiders.
764 @itemx --timeout=@var{seconds}
765 Set the network timeout to @var{seconds} seconds. This is equivalent
766 to specifying @samp{--dns-timeout}, @samp{--connect-timeout}, and
767 @samp{--read-timeout}, all at the same time.
769 When interacting with the network, Wget can check for timeout and
770 abort the operation if it takes too long. This prevents anomalies
771 like hanging reads and infinite connects. The only timeout enabled by
772 default is a 900-second read timeout. Setting a timeout to 0 disables
773 it altogether. Unless you know what you are doing, it is best not to
774 change the default timeout settings.
776 All timeout-related options accept decimal values, as well as
777 subsecond values. For example, @samp{0.1} seconds is a legal (though
778 unwise) choice of timeout. Subsecond timeouts are useful for checking
779 server response times or for testing network latency.
783 @item --dns-timeout=@var{seconds}
784 Set the DNS lookup timeout to @var{seconds} seconds. DNS lookups that
785 don't complete within the specified time will fail. By default, there
786 is no timeout on DNS lookups, other than that implemented by system
789 @cindex connect timeout
790 @cindex timeout, connect
791 @item --connect-timeout=@var{seconds}
792 Set the connect timeout to @var{seconds} seconds. TCP connections that
793 take longer to establish will be aborted. By default, there is no
794 connect timeout, other than that implemented by system libraries.
797 @cindex timeout, read
798 @item --read-timeout=@var{seconds}
799 Set the read (and write) timeout to @var{seconds} seconds. The
800 ``time'' of this timeout refers to @dfn{idle time}: if, at any point in
801 the download, no data is received for more than the specified number
802 of seconds, reading fails and the download is restarted. This option
803 does not directly affect the duration of the entire download.
805 Of course, the remote server may choose to terminate the connection
806 sooner than this option requires. The default read timeout is 900
809 @cindex bandwidth, limit
811 @cindex limit bandwidth
812 @item --limit-rate=@var{amount}
813 Limit the download speed to @var{amount} bytes per second. Amount may
814 be expressed in bytes, kilobytes with the @samp{k} suffix, or megabytes
815 with the @samp{m} suffix. For example, @samp{--limit-rate=20k} will
816 limit the retrieval rate to 20KB/s. This is useful when, for whatever
817 reason, you don't want Wget to consume the entire available bandwidth.
819 This option allows the use of decimal numbers, usually in conjunction
820 with power suffixes; for example, @samp{--limit-rate=2.5k} is a legal
823 Note that Wget implements the limiting by sleeping the appropriate
824 amount of time after a network read that took less time than specified
825 by the rate. Eventually this strategy causes the TCP transfer to slow
826 down to approximately the specified rate. However, it may take some
827 time for this balance to be achieved, so don't be surprised if limiting
828 the rate doesn't work well with very small files.
832 @item -w @var{seconds}
833 @itemx --wait=@var{seconds}
834 Wait the specified number of seconds between the retrievals. Use of
835 this option is recommended, as it lightens the server load by making the
836 requests less frequent. Instead of in seconds, the time can be
837 specified in minutes using the @code{m} suffix, in hours using @code{h}
838 suffix, or in days using @code{d} suffix.
840 Specifying a large value for this option is useful if the network or the
841 destination host is down, so that Wget can wait long enough to
842 reasonably expect the network error to be fixed before the retry. The
843 waiting interval specified by this function is influenced by
844 @code{--random-wait}, which see.
846 @cindex retries, waiting between
847 @cindex waiting between retries
848 @item --waitretry=@var{seconds}
849 If you don't want Wget to wait between @emph{every} retrieval, but only
850 between retries of failed downloads, you can use this option. Wget will
851 use @dfn{linear backoff}, waiting 1 second after the first failure on a
852 given file, then waiting 2 seconds after the second failure on that
853 file, up to the maximum number of @var{seconds} you specify.
855 By default, Wget will assume a value of 10 seconds.
860 Some web sites may perform log analysis to identify retrieval programs
861 such as Wget by looking for statistically significant similarities in
862 the time between requests. This option causes the time between requests
863 to vary between 0.5 and 1.5 * @var{wait} seconds, where @var{wait} was
864 specified using the @samp{--wait} option, in order to mask Wget's
865 presence from such analysis.
867 A 2001 article in a publication devoted to development on a popular
868 consumer platform provided code to perform this analysis on the fly.
869 Its author suggested blocking at the class C address level to ensure
870 automated retrieval programs were blocked despite changing DHCP-supplied
873 The @samp{--random-wait} option was inspired by this ill-advised
874 recommendation to block many unrelated users from a web site due to the
879 Don't use proxies, even if the appropriate @code{*_proxy} environment
883 For more information about the use of proxies with Wget, @xref{Proxies}.
888 @itemx --quota=@var{quota}
889 Specify download quota for automatic retrievals. The value can be
890 specified in bytes (default), kilobytes (with @samp{k} suffix), or
891 megabytes (with @samp{m} suffix).
893 Note that quota will never affect downloading a single file. So if you
894 specify @samp{wget -Q10k ftp://wuarchive.wustl.edu/ls-lR.gz}, all of the
895 @file{ls-lR.gz} will be downloaded. The same goes even when several
896 @sc{url}s are specified on the command-line. However, quota is
897 respected when retrieving either recursively, or from an input file.
898 Thus you may safely type @samp{wget -Q2m -i sites}---download will be
899 aborted when the quota is exceeded.
901 Setting quota to 0 or to @samp{inf} unlimits the download quota.
904 @cindex caching of DNS lookups
906 Turn off caching of DNS lookups. Normally, Wget remembers the IP
907 addresses it looked up from DNS so it doesn't have to repeatedly
908 contact the DNS server for the same (typically small) set of hosts it
909 retrieves from. This cache exists in memory only; a new Wget run will
912 However, it has been reported that in some situations it is not
913 desirable to cache host names, even for the duration of a
914 short-running application like Wget. With this option Wget issues a
915 new DNS lookup (more precisely, a new call to @code{gethostbyname} or
916 @code{getaddrinfo}) each time it makes a new connection. Please note
917 that this option will @emph{not} affect caching that might be
918 performed by the resolving library or by an external caching layer,
921 If you don't understand exactly what this option does, you probably
924 @cindex file names, restrict
925 @cindex Windows file names
926 @item --restrict-file-names=@var{modes}
927 Change which characters found in remote URLs must be escaped during
928 generation of local filenames. Characters that are @dfn{restricted}
929 by this option are escaped, i.e. replaced with @samp{%HH}, where
930 @samp{HH} is the hexadecimal number that corresponds to the restricted
931 character. This option may also be used to force all alphabetical
932 cases to be either lower- or uppercase.
934 By default, Wget escapes the characters that are not valid or safe as
935 part of file names on your operating system, as well as control
936 characters that are typically unprintable. This option is useful for
937 changing these defaults, perhaps because you are downloading to a
938 non-native partition, or because you want to disable escaping of the
939 control characters, or you want to further restrict characters to only
940 those in the @sc{ascii} range of values.
942 The @var{modes} are a comma-separated set of text values. The
943 acceptable values are @samp{unix}, @samp{windows}, @samp{nocontrol},
944 @samp{ascii}, @samp{lowercase}, and @samp{uppercase}. The values
945 @samp{unix} and @samp{windows} are mutually exclusive (one will
946 override the other), as are @samp{lowercase} and
947 @samp{uppercase}. Those last are special cases, as they do not change
948 the set of characters that would be escaped, but rather force local
949 file paths to be converted either to lower- or uppercase.
951 When ``unix'' is specified, Wget escapes the character @samp{/} and
952 the control characters in the ranges 0--31 and 128--159. This is the
953 default on Unix-like operating systems.
955 When ``windows'' is given, Wget escapes the characters @samp{\},
956 @samp{|}, @samp{/}, @samp{:}, @samp{?}, @samp{"}, @samp{*}, @samp{<},
957 @samp{>}, and the control characters in the ranges 0--31 and 128--159.
958 In addition to this, Wget in Windows mode uses @samp{+} instead of
959 @samp{:} to separate host and port in local file names, and uses
960 @samp{@@} instead of @samp{?} to separate the query portion of the file
961 name from the rest. Therefore, a URL that would be saved as
962 @samp{www.xemacs.org:4300/search.pl?input=blah} in Unix mode would be
963 saved as @samp{www.xemacs.org+4300/search.pl@@input=blah} in Windows
964 mode. This mode is the default on Windows.
966 If you specify @samp{nocontrol}, then the escaping of the control
967 characters is also switched off. This option may make sense
968 when you are downloading URLs whose names contain UTF-8 characters, on
969 a system which can save and display filenames in UTF-8 (some possible
970 byte values used in UTF-8 byte sequences fall in the range of values
971 designated by Wget as ``controls'').
973 The @samp{ascii} mode is used to specify that any bytes whose values
974 are outside the range of @sc{ascii} characters (that is, greater than
975 127) shall be escaped. This can be useful when saving filenames
976 whose encoding does not match the one used locally.
983 Force connecting to IPv4 or IPv6 addresses. With @samp{--inet4-only}
984 or @samp{-4}, Wget will only connect to IPv4 hosts, ignoring AAAA
985 records in DNS, and refusing to connect to IPv6 addresses specified in
986 URLs. Conversely, with @samp{--inet6-only} or @samp{-6}, Wget will
987 only connect to IPv6 hosts and ignore A records and IPv4 addresses.
989 Neither options should be needed normally. By default, an IPv6-aware
990 Wget will use the address family specified by the host's DNS record.
991 If the DNS responds with both IPv4 and IPv6 addresses, Wget will try
992 them in sequence until it finds one it can connect to. (Also see
993 @code{--prefer-family} option described below.)
995 These options can be used to deliberately force the use of IPv4 or
996 IPv6 address families on dual family systems, usually to aid debugging
997 or to deal with broken network configuration. Only one of
998 @samp{--inet6-only} and @samp{--inet4-only} may be specified at the
999 same time. Neither option is available in Wget compiled without IPv6
1002 @item --prefer-family=none/IPv4/IPv6
1003 When given a choice of several addresses, connect to the addresses
1004 with specified address family first. The address order returned by
1005 DNS is used without change by default.
1007 This avoids spurious errors and connect attempts when accessing hosts
1008 that resolve to both IPv6 and IPv4 addresses from IPv4 networks. For
1009 example, @samp{www.kame.net} resolves to
1010 @samp{2001:200:0:8002:203:47ff:fea5:3085} and to
1011 @samp{203.178.141.194}. When the preferred family is @code{IPv4}, the
1012 IPv4 address is used first; when the preferred family is @code{IPv6},
1013 the IPv6 address is used first; if the specified value is @code{none},
1014 the address order returned by DNS is used without change.
1016 Unlike @samp{-4} and @samp{-6}, this option doesn't inhibit access to
1017 any address family, it only changes the @emph{order} in which the
1018 addresses are accessed. Also note that the reordering performed by
1019 this option is @dfn{stable}---it doesn't affect order of addresses of
1020 the same family. That is, the relative order of all IPv4 addresses
1021 and of all IPv6 addresses remains intact in all cases.
1023 @item --retry-connrefused
1024 Consider ``connection refused'' a transient error and try again.
1025 Normally Wget gives up on a URL when it is unable to connect to the
1026 site because failure to connect is taken as a sign that the server is
1027 not running at all and that retries would not help. This option is
1028 for mirroring unreliable sites whose servers tend to disappear for
1029 short periods of time.
1033 @cindex authentication
1034 @item --user=@var{user}
1035 @itemx --password=@var{password}
1036 Specify the username @var{user} and password @var{password} for both
1037 @sc{ftp} and @sc{http} file retrieval. These parameters can be overridden
1038 using the @samp{--ftp-user} and @samp{--ftp-password} options for
1039 @sc{ftp} connections and the @samp{--http-user} and @samp{--http-password}
1040 options for @sc{http} connections.
1042 @item --ask-password
1043 Prompt for a password for each connection established. Cannot be specified
1044 when @samp{--password} is being used, because they are mutually exclusive.
1050 Turn off internationalized URI (IRI) support. Use @samp{--iri} to
1051 turn it on. IRI support is activated by default.
1053 You can set the default state of IRI support using the @code{iri}
1054 command in @file{.wgetrc}. That setting may be overridden from the
1057 @cindex local encoding
1058 @item --local-encoding=@var{encoding}
1060 Force Wget to use @var{encoding} as the default system encoding. That affects
1061 how Wget converts URLs specified as arguments from locale to @sc{utf-8} for
1064 Wget use the function @code{nl_langinfo()} and then the @code{CHARSET}
1065 environment variable to get the locale. If it fails, @sc{ascii} is used.
1067 You can set the default local encoding using the @code{local_encoding}
1068 command in @file{.wgetrc}. That setting may be overridden from the
1071 @cindex remote encoding
1072 @item --remote-encoding=@var{encoding}
1074 Force Wget to use @var{encoding} as the default remote server encoding.
1075 That affects how Wget converts URIs found in files from remote encoding
1076 to @sc{utf-8} during a recursive fetch. This options is only useful for
1077 IRI support, for the interpretation of non-@sc{ascii} characters.
1079 For HTTP, remote encoding can be found in HTTP @code{Content-Type}
1080 header and in HTML @code{Content-Type http-equiv} meta tag.
1082 You can set the default encoding using the @code{remoteencoding}
1083 command in @file{.wgetrc}. That setting may be overridden from the
1089 Force Wget to unlink file instead of clobbering existing file. This
1090 option is useful for downloading to the directory with hardlinks.
1094 @node Directory Options, HTTP Options, Download Options, Invoking
1095 @section Directory Options
1099 @itemx --no-directories
1100 Do not create a hierarchy of directories when retrieving recursively.
1101 With this option turned on, all files will get saved to the current
1102 directory, without clobbering (if a name shows up more than once, the
1103 filenames will get extensions @samp{.n}).
1106 @itemx --force-directories
1107 The opposite of @samp{-nd}---create a hierarchy of directories, even if
1108 one would not have been created otherwise. E.g. @samp{wget -x
1109 http://fly.srk.fer.hr/robots.txt} will save the downloaded file to
1110 @file{fly.srk.fer.hr/robots.txt}.
1113 @itemx --no-host-directories
1114 Disable generation of host-prefixed directories. By default, invoking
1115 Wget with @samp{-r http://fly.srk.fer.hr/} will create a structure of
1116 directories beginning with @file{fly.srk.fer.hr/}. This option disables
1119 @item --protocol-directories
1120 Use the protocol name as a directory component of local file names. For
1121 example, with this option, @samp{wget -r http://@var{host}} will save to
1122 @samp{http/@var{host}/...} rather than just to @samp{@var{host}/...}.
1124 @cindex cut directories
1125 @item --cut-dirs=@var{number}
1126 Ignore @var{number} directory components. This is useful for getting a
1127 fine-grained control over the directory where recursive retrieval will
1130 Take, for example, the directory at
1131 @samp{ftp://ftp.xemacs.org/pub/xemacs/}. If you retrieve it with
1132 @samp{-r}, it will be saved locally under
1133 @file{ftp.xemacs.org/pub/xemacs/}. While the @samp{-nH} option can
1134 remove the @file{ftp.xemacs.org/} part, you are still stuck with
1135 @file{pub/xemacs}. This is where @samp{--cut-dirs} comes in handy; it
1136 makes Wget not ``see'' @var{number} remote directory components. Here
1137 are several examples of how @samp{--cut-dirs} option works.
1141 No options -> ftp.xemacs.org/pub/xemacs/
1143 -nH --cut-dirs=1 -> xemacs/
1144 -nH --cut-dirs=2 -> .
1146 --cut-dirs=1 -> ftp.xemacs.org/xemacs/
1151 If you just want to get rid of the directory structure, this option is
1152 similar to a combination of @samp{-nd} and @samp{-P}. However, unlike
1153 @samp{-nd}, @samp{--cut-dirs} does not lose with subdirectories---for
1154 instance, with @samp{-nH --cut-dirs=1}, a @file{beta/} subdirectory will
1155 be placed to @file{xemacs/beta}, as one would expect.
1157 @cindex directory prefix
1158 @item -P @var{prefix}
1159 @itemx --directory-prefix=@var{prefix}
1160 Set directory prefix to @var{prefix}. The @dfn{directory prefix} is the
1161 directory where all other files and subdirectories will be saved to,
1162 i.e. the top of the retrieval tree. The default is @samp{.} (the
1166 @node HTTP Options, HTTPS (SSL/TLS) Options, Directory Options, Invoking
1167 @section HTTP Options
1170 @cindex default page name
1172 @item --default-page=@var{name}
1173 Use @var{name} as the default file name when it isn't known (i.e., for
1174 URLs that end in a slash), instead of @file{index.html}.
1176 @cindex .html extension
1177 @cindex .css extension
1179 @itemx --adjust-extension
1180 If a file of type @samp{application/xhtml+xml} or @samp{text/html} is
1181 downloaded and the URL does not end with the regexp
1182 @samp{\.[Hh][Tt][Mm][Ll]?}, this option will cause the suffix @samp{.html}
1183 to be appended to the local filename. This is useful, for instance, when
1184 you're mirroring a remote site that uses @samp{.asp} pages, but you want
1185 the mirrored pages to be viewable on your stock Apache server. Another
1186 good use for this is when you're downloading CGI-generated materials. A URL
1187 like @samp{http://site.com/article.cgi?25} will be saved as
1188 @file{article.cgi?25.html}.
1190 Note that filenames changed in this way will be re-downloaded every time
1191 you re-mirror a site, because Wget can't tell that the local
1192 @file{@var{X}.html} file corresponds to remote URL @samp{@var{X}} (since
1193 it doesn't yet know that the URL produces output of type
1194 @samp{text/html} or @samp{application/xhtml+xml}.
1196 As of version 1.12, Wget will also ensure that any downloaded files of
1197 type @samp{text/css} end in the suffix @samp{.css}, and the option was
1198 renamed from @samp{--html-extension}, to better reflect its new
1199 behavior. The old option name is still acceptable, but should now be
1200 considered deprecated.
1202 At some point in the future, this option may well be expanded to
1203 include suffixes for other types of content, including content types
1204 that are not parsed by Wget.
1207 @cindex http password
1208 @cindex authentication
1209 @item --http-user=@var{user}
1210 @itemx --http-password=@var{password}
1211 Specify the username @var{user} and password @var{password} on an
1212 @sc{http} server. According to the type of the challenge, Wget will
1213 encode them using either the @code{basic} (insecure),
1214 the @code{digest}, or the Windows @code{NTLM} authentication scheme.
1216 Another way to specify username and password is in the @sc{url} itself
1217 (@pxref{URL Format}). Either method reveals your password to anyone who
1218 bothers to run @code{ps}. To prevent the passwords from being seen,
1219 store them in @file{.wgetrc} or @file{.netrc}, and make sure to protect
1220 those files from other users with @code{chmod}. If the passwords are
1221 really important, do not leave them lying in those files either---edit
1222 the files and delete them after Wget has started the download.
1225 For more information about security issues with Wget, @xref{Security
1229 @cindex Keep-Alive, turning off
1230 @cindex Persistent Connections, disabling
1231 @item --no-http-keep-alive
1232 Turn off the ``keep-alive'' feature for HTTP downloads. Normally, Wget
1233 asks the server to keep the connection open so that, when you download
1234 more than one document from the same server, they get transferred over
1235 the same TCP connection. This saves time and at the same time reduces
1236 the load on the server.
1238 This option is useful when, for some reason, persistent (keep-alive)
1239 connections don't work for you, for example due to a server bug or due
1240 to the inability of server-side scripts to cope with the connections.
1245 Disable server-side cache. In this case, Wget will send the remote
1246 server an appropriate directive (@samp{Pragma: no-cache}) to get the
1247 file from the remote service, rather than returning the cached version.
1248 This is especially useful for retrieving and flushing out-of-date
1249 documents on proxy servers.
1251 Caching is allowed by default.
1255 Disable the use of cookies. Cookies are a mechanism for maintaining
1256 server-side state. The server sends the client a cookie using the
1257 @code{Set-Cookie} header, and the client responds with the same cookie
1258 upon further requests. Since cookies allow the server owners to keep
1259 track of visitors and for sites to exchange this information, some
1260 consider them a breach of privacy. The default is to use cookies;
1261 however, @emph{storing} cookies is not on by default.
1263 @cindex loading cookies
1264 @cindex cookies, loading
1265 @item --load-cookies @var{file}
1266 Load cookies from @var{file} before the first HTTP retrieval.
1267 @var{file} is a textual file in the format originally used by Netscape's
1268 @file{cookies.txt} file.
1270 You will typically use this option when mirroring sites that require
1271 that you be logged in to access some or all of their content. The login
1272 process typically works by the web server issuing an @sc{http} cookie
1273 upon receiving and verifying your credentials. The cookie is then
1274 resent by the browser when accessing that part of the site, and so
1275 proves your identity.
1277 Mirroring such a site requires Wget to send the same cookies your
1278 browser sends when communicating with the site. This is achieved by
1279 @samp{--load-cookies}---simply point Wget to the location of the
1280 @file{cookies.txt} file, and it will send the same cookies your browser
1281 would send in the same situation. Different browsers keep textual
1282 cookie files in different locations:
1286 The cookies are in @file{~/.netscape/cookies.txt}.
1288 @item Mozilla and Netscape 6.x.
1289 Mozilla's cookie file is also named @file{cookies.txt}, located
1290 somewhere under @file{~/.mozilla}, in the directory of your profile.
1291 The full path usually ends up looking somewhat like
1292 @file{~/.mozilla/default/@var{some-weird-string}/cookies.txt}.
1294 @item Internet Explorer.
1295 You can produce a cookie file Wget can use by using the File menu,
1296 Import and Export, Export Cookies. This has been tested with Internet
1297 Explorer 5; it is not guaranteed to work with earlier versions.
1299 @item Other browsers.
1300 If you are using a different browser to create your cookies,
1301 @samp{--load-cookies} will only work if you can locate or produce a
1302 cookie file in the Netscape format that Wget expects.
1305 If you cannot use @samp{--load-cookies}, there might still be an
1306 alternative. If your browser supports a ``cookie manager'', you can use
1307 it to view the cookies used when accessing the site you're mirroring.
1308 Write down the name and value of the cookie, and manually instruct Wget
1309 to send those cookies, bypassing the ``official'' cookie support:
1312 wget --no-cookies --header "Cookie: @var{name}=@var{value}"
1315 @cindex saving cookies
1316 @cindex cookies, saving
1317 @item --save-cookies @var{file}
1318 Save cookies to @var{file} before exiting. This will not save cookies
1319 that have expired or that have no expiry time (so-called ``session
1320 cookies''), but also see @samp{--keep-session-cookies}.
1322 @cindex cookies, session
1323 @cindex session cookies
1324 @item --keep-session-cookies
1325 When specified, causes @samp{--save-cookies} to also save session
1326 cookies. Session cookies are normally not saved because they are
1327 meant to be kept in memory and forgotten when you exit the browser.
1328 Saving them is useful on sites that require you to log in or to visit
1329 the home page before you can access some pages. With this option,
1330 multiple Wget runs are considered a single browser session as far as
1331 the site is concerned.
1333 Since the cookie file format does not normally carry session cookies,
1334 Wget marks them with an expiry timestamp of 0. Wget's
1335 @samp{--load-cookies} recognizes those as session cookies, but it might
1336 confuse other browsers. Also note that cookies so loaded will be
1337 treated as other session cookies, which means that if you want
1338 @samp{--save-cookies} to preserve them again, you must use
1339 @samp{--keep-session-cookies} again.
1341 @cindex Content-Length, ignore
1342 @cindex ignore length
1343 @item --ignore-length
1344 Unfortunately, some @sc{http} servers (@sc{cgi} programs, to be more
1345 precise) send out bogus @code{Content-Length} headers, which makes Wget
1346 go wild, as it thinks not all the document was retrieved. You can spot
1347 this syndrome if Wget retries getting the same document again and again,
1348 each time claiming that the (otherwise normal) connection has closed on
1351 With this option, Wget will ignore the @code{Content-Length} header---as
1352 if it never existed.
1355 @item --header=@var{header-line}
1356 Send @var{header-line} along with the rest of the headers in each
1357 @sc{http} request. The supplied header is sent as-is, which means it
1358 must contain name and value separated by colon, and must not contain
1361 You may define more than one additional header by specifying
1362 @samp{--header} more than once.
1366 wget --header='Accept-Charset: iso-8859-2' \
1367 --header='Accept-Language: hr' \
1368 http://fly.srk.fer.hr/
1372 Specification of an empty string as the header value will clear all
1373 previous user-defined headers.
1375 As of Wget 1.10, this option can be used to override headers otherwise
1376 generated automatically. This example instructs Wget to connect to
1377 localhost, but to specify @samp{foo.bar} in the @code{Host} header:
1380 wget --header="Host: foo.bar" http://localhost/
1383 In versions of Wget prior to 1.10 such use of @samp{--header} caused
1384 sending of duplicate headers.
1387 @item --max-redirect=@var{number}
1388 Specifies the maximum number of redirections to follow for a resource.
1389 The default is 20, which is usually far more than necessary. However, on
1390 those occasions where you want to allow more (or fewer), this is the
1394 @cindex proxy password
1395 @cindex proxy authentication
1396 @item --proxy-user=@var{user}
1397 @itemx --proxy-password=@var{password}
1398 Specify the username @var{user} and password @var{password} for
1399 authentication on a proxy server. Wget will encode them using the
1400 @code{basic} authentication scheme.
1402 Security considerations similar to those with @samp{--http-password}
1403 pertain here as well.
1405 @cindex http referer
1406 @cindex referer, http
1407 @item --referer=@var{url}
1408 Include `Referer: @var{url}' header in HTTP request. Useful for
1409 retrieving documents with server-side processing that assume they are
1410 always being retrieved by interactive web browsers and only come out
1411 properly when Referer is set to one of the pages that point to them.
1413 @cindex server response, save
1414 @item --save-headers
1415 Save the headers sent by the @sc{http} server to the file, preceding the
1416 actual contents, with an empty line as the separator.
1419 @item -U @var{agent-string}
1420 @itemx --user-agent=@var{agent-string}
1421 Identify as @var{agent-string} to the @sc{http} server.
1423 The @sc{http} protocol allows the clients to identify themselves using a
1424 @code{User-Agent} header field. This enables distinguishing the
1425 @sc{www} software, usually for statistical purposes or for tracing of
1426 protocol violations. Wget normally identifies as
1427 @samp{Wget/@var{version}}, @var{version} being the current version
1430 However, some sites have been known to impose the policy of tailoring
1431 the output according to the @code{User-Agent}-supplied information.
1432 While this is not such a bad idea in theory, it has been abused by
1433 servers denying information to clients other than (historically)
1434 Netscape or, more frequently, Microsoft Internet Explorer. This
1435 option allows you to change the @code{User-Agent} line issued by Wget.
1436 Use of this option is discouraged, unless you really know what you are
1439 Specifying empty user agent with @samp{--user-agent=""} instructs Wget
1440 not to send the @code{User-Agent} header in @sc{http} requests.
1443 @item --post-data=@var{string}
1444 @itemx --post-file=@var{file}
1445 Use POST as the method for all HTTP requests and send the specified
1446 data in the request body. @samp{--post-data} sends @var{string} as
1447 data, whereas @samp{--post-file} sends the contents of @var{file}.
1448 Other than that, they work in exactly the same way. In particular,
1449 they @emph{both} expect content of the form @code{key1=value1&key2=value2},
1450 with percent-encoding for special characters; the only difference is
1451 that one expects its content as a command-line parameter and the other
1452 accepts its content from a file. In particular, @samp{--post-file} is
1453 @emph{not} for transmitting files as form attachments: those must
1454 appear as @code{key=value} data (with appropriate percent-coding) just
1455 like everything else. Wget does not currently support
1456 @code{multipart/form-data} for transmitting POST data; only
1457 @code{application/x-www-form-urlencoded}. Only one of
1458 @samp{--post-data} and @samp{--post-file} should be specified.
1460 Please be aware that Wget needs to know the size of the POST data in
1461 advance. Therefore the argument to @code{--post-file} must be a regular
1462 file; specifying a FIFO or something like @file{/dev/stdin} won't work.
1463 It's not quite clear how to work around this limitation inherent in
1464 HTTP/1.0. Although HTTP/1.1 introduces @dfn{chunked} transfer that
1465 doesn't require knowing the request length in advance, a client can't
1466 use chunked unless it knows it's talking to an HTTP/1.1 server. And it
1467 can't know that until it receives a response, which in turn requires the
1468 request to have been completed -- a chicken-and-egg problem.
1470 Note: if Wget is redirected after the POST request is completed, it
1471 will not send the POST data to the redirected URL. This is because
1472 URLs that process POST often respond with a redirection to a regular
1473 page, which does not desire or accept POST. It is not completely
1474 clear that this behavior is optimal; if it doesn't work out, it might
1475 be changed in the future.
1477 This example shows how to log to a server using POST and then proceed to
1478 download the desired pages, presumably only accessible to authorized
1483 # @r{Log in to the server. This can be done only once.}
1484 wget --save-cookies cookies.txt \
1485 --post-data 'user=foo&password=bar' \
1486 http://server.com/auth.php
1488 # @r{Now grab the page or pages we care about.}
1489 wget --load-cookies cookies.txt \
1490 -p http://server.com/interesting/article.php
1494 If the server is using session cookies to track user authentication,
1495 the above will not work because @samp{--save-cookies} will not save
1496 them (and neither will browsers) and the @file{cookies.txt} file will
1497 be empty. In that case use @samp{--keep-session-cookies} along with
1498 @samp{--save-cookies} to force saving of session cookies.
1500 @cindex Content-Disposition
1501 @item --content-disposition
1503 If this is set to on, experimental (not fully-functional) support for
1504 @code{Content-Disposition} headers is enabled. This can currently result in
1505 extra round-trips to the server for a @code{HEAD} request, and is known
1506 to suffer from a few bugs, which is why it is not currently enabled by default.
1508 This option is useful for some file-downloading CGI programs that use
1509 @code{Content-Disposition} headers to describe what the name of a
1510 downloaded file should be.
1512 @cindex Content On Error
1513 @item --content-on-error
1515 If this is set to on, wget will not skip the content when the server responds
1516 with a http status code that indicates error.
1518 @cindex Trust server names
1519 @item --trust-server-names
1521 If this is set to on, on a redirect the last component of the
1522 redirection URL will be used as the local file name. By default it is
1523 used the last component in the original URL.
1525 @cindex authentication
1526 @item --auth-no-challenge
1528 If this option is given, Wget will send Basic HTTP authentication
1529 information (plaintext username and password) for all requests, just
1530 like Wget 1.10.2 and prior did by default.
1532 Use of this option is not recommended, and is intended only to support
1533 some few obscure servers, which never send HTTP authentication
1534 challenges, but accept unsolicited auth info, say, in addition to
1535 form-based authentication.
1539 @node HTTPS (SSL/TLS) Options, FTP Options, HTTP Options, Invoking
1540 @section HTTPS (SSL/TLS) Options
1543 To support encrypted HTTP (HTTPS) downloads, Wget must be compiled
1544 with an external SSL library, currently OpenSSL. If Wget is compiled
1545 without SSL support, none of these options are available.
1548 @cindex SSL protocol, choose
1549 @item --secure-protocol=@var{protocol}
1550 Choose the secure protocol to be used. Legal values are @samp{auto},
1551 @samp{SSLv2}, @samp{SSLv3}, and @samp{TLSv1}. If @samp{auto} is used,
1552 the SSL library is given the liberty of choosing the appropriate
1553 protocol automatically, which is achieved by sending an SSLv2 greeting
1554 and announcing support for SSLv3 and TLSv1. This is the default.
1556 Specifying @samp{SSLv2}, @samp{SSLv3}, or @samp{TLSv1} forces the use
1557 of the corresponding protocol. This is useful when talking to old and
1558 buggy SSL server implementations that make it hard for OpenSSL to
1559 choose the correct protocol version. Fortunately, such servers are
1562 @cindex SSL certificate, check
1563 @item --no-check-certificate
1564 Don't check the server certificate against the available certificate
1565 authorities. Also don't require the URL host name to match the common
1566 name presented by the certificate.
1568 As of Wget 1.10, the default is to verify the server's certificate
1569 against the recognized certificate authorities, breaking the SSL
1570 handshake and aborting the download if the verification fails.
1571 Although this provides more secure downloads, it does break
1572 interoperability with some sites that worked with previous Wget
1573 versions, particularly those using self-signed, expired, or otherwise
1574 invalid certificates. This option forces an ``insecure'' mode of
1575 operation that turns the certificate verification errors into warnings
1576 and allows you to proceed.
1578 If you encounter ``certificate verification'' errors or ones saying
1579 that ``common name doesn't match requested host name'', you can use
1580 this option to bypass the verification and proceed with the download.
1581 @emph{Only use this option if you are otherwise convinced of the
1582 site's authenticity, or if you really don't care about the validity of
1583 its certificate.} It is almost always a bad idea not to check the
1584 certificates when transmitting confidential or important data.
1586 @cindex SSL certificate
1587 @item --certificate=@var{file}
1588 Use the client certificate stored in @var{file}. This is needed for
1589 servers that are configured to require certificates from the clients
1590 that connect to them. Normally a certificate is not required and this
1593 @cindex SSL certificate type, specify
1594 @item --certificate-type=@var{type}
1595 Specify the type of the client certificate. Legal values are
1596 @samp{PEM} (assumed by default) and @samp{DER}, also known as
1599 @item --private-key=@var{file}
1600 Read the private key from @var{file}. This allows you to provide the
1601 private key in a file separate from the certificate.
1603 @item --private-key-type=@var{type}
1604 Specify the type of the private key. Accepted values are @samp{PEM}
1605 (the default) and @samp{DER}.
1607 @item --ca-certificate=@var{file}
1608 Use @var{file} as the file with the bundle of certificate authorities
1609 (``CA'') to verify the peers. The certificates must be in PEM format.
1611 Without this option Wget looks for CA certificates at the
1612 system-specified locations, chosen at OpenSSL installation time.
1614 @cindex SSL certificate authority
1615 @item --ca-directory=@var{directory}
1616 Specifies directory containing CA certificates in PEM format. Each
1617 file contains one CA certificate, and the file name is based on a hash
1618 value derived from the certificate. This is achieved by processing a
1619 certificate directory with the @code{c_rehash} utility supplied with
1620 OpenSSL. Using @samp{--ca-directory} is more efficient than
1621 @samp{--ca-certificate} when many certificates are installed because
1622 it allows Wget to fetch certificates on demand.
1624 Without this option Wget looks for CA certificates at the
1625 system-specified locations, chosen at OpenSSL installation time.
1627 @cindex entropy, specifying source of
1628 @cindex randomness, specifying source of
1629 @item --random-file=@var{file}
1630 Use @var{file} as the source of random data for seeding the
1631 pseudo-random number generator on systems without @file{/dev/random}.
1633 On such systems the SSL library needs an external source of randomness
1634 to initialize. Randomness may be provided by EGD (see
1635 @samp{--egd-file} below) or read from an external source specified by
1636 the user. If this option is not specified, Wget looks for random data
1637 in @code{$RANDFILE} or, if that is unset, in @file{$HOME/.rnd}. If
1638 none of those are available, it is likely that SSL encryption will not
1641 If you're getting the ``Could not seed OpenSSL PRNG; disabling SSL.''
1642 error, you should provide random data using some of the methods
1646 @item --egd-file=@var{file}
1647 Use @var{file} as the EGD socket. EGD stands for @dfn{Entropy
1648 Gathering Daemon}, a user-space program that collects data from
1649 various unpredictable system sources and makes it available to other
1650 programs that might need it. Encryption software, such as the SSL
1651 library, needs sources of non-repeating randomness to seed the random
1652 number generator used to produce cryptographically strong keys.
1654 OpenSSL allows the user to specify his own source of entropy using the
1655 @code{RAND_FILE} environment variable. If this variable is unset, or
1656 if the specified file does not produce enough randomness, OpenSSL will
1657 read random data from EGD socket specified using this option.
1659 If this option is not specified (and the equivalent startup command is
1660 not used), EGD is never contacted. EGD is not needed on modern Unix
1661 systems that support @file{/dev/random}.
1666 @item --warc-file=@var{file}
1667 Use @var{file} as the destination WARC file.
1669 @item --warc-header=@var{string}
1670 Use @var{string} into as the warcinfo record.
1672 @item --warc-max-size=@var{size}
1673 Set the maximum size of the WARC files to @var{size}.
1676 Write CDX index files.
1678 @item --warc-dedup=@var{file}
1679 Do not store records listed in this CDX file.
1681 @item --no-warc-compression
1682 Do not compress WARC files with GZIP.
1684 @item --no-warc-digests
1685 Do not calculate SHA1 digests.
1687 @item --no-warc-keep-log
1688 Do not store the log file in a WARC record.
1690 @item --warc-tempdir=@var{dir}
1691 Specify the location for temporary files created by the WARC writer.
1694 @node FTP Options, Recursive Retrieval Options, HTTPS (SSL/TLS) Options, Invoking
1695 @section FTP Options
1699 @cindex ftp password
1700 @cindex ftp authentication
1701 @item --ftp-user=@var{user}
1702 @itemx --ftp-password=@var{password}
1703 Specify the username @var{user} and password @var{password} on an
1704 @sc{ftp} server. Without this, or the corresponding startup option,
1705 the password defaults to @samp{-wget@@}, normally used for anonymous
1708 Another way to specify username and password is in the @sc{url} itself
1709 (@pxref{URL Format}). Either method reveals your password to anyone who
1710 bothers to run @code{ps}. To prevent the passwords from being seen,
1711 store them in @file{.wgetrc} or @file{.netrc}, and make sure to protect
1712 those files from other users with @code{chmod}. If the passwords are
1713 really important, do not leave them lying in those files either---edit
1714 the files and delete them after Wget has started the download.
1717 For more information about security issues with Wget, @xref{Security
1721 @cindex .listing files, removing
1722 @item --no-remove-listing
1723 Don't remove the temporary @file{.listing} files generated by @sc{ftp}
1724 retrievals. Normally, these files contain the raw directory listings
1725 received from @sc{ftp} servers. Not removing them can be useful for
1726 debugging purposes, or when you want to be able to easily check on the
1727 contents of remote server directories (e.g. to verify that a mirror
1728 you're running is complete).
1730 Note that even though Wget writes to a known filename for this file,
1731 this is not a security hole in the scenario of a user making
1732 @file{.listing} a symbolic link to @file{/etc/passwd} or something and
1733 asking @code{root} to run Wget in his or her directory. Depending on
1734 the options used, either Wget will refuse to write to @file{.listing},
1735 making the globbing/recursion/time-stamping operation fail, or the
1736 symbolic link will be deleted and replaced with the actual
1737 @file{.listing} file, or the listing will be written to a
1738 @file{.listing.@var{number}} file.
1740 Even though this situation isn't a problem, though, @code{root} should
1741 never run Wget in a non-trusted user's directory. A user could do
1742 something as simple as linking @file{index.html} to @file{/etc/passwd}
1743 and asking @code{root} to run Wget with @samp{-N} or @samp{-r} so the file
1744 will be overwritten.
1746 @cindex globbing, toggle
1748 Turn off @sc{ftp} globbing. Globbing refers to the use of shell-like
1749 special characters (@dfn{wildcards}), like @samp{*}, @samp{?}, @samp{[}
1750 and @samp{]} to retrieve more than one file from the same directory at
1754 wget ftp://gnjilux.srk.fer.hr/*.msg
1757 By default, globbing will be turned on if the @sc{url} contains a
1758 globbing character. This option may be used to turn globbing on or off
1761 You may have to quote the @sc{url} to protect it from being expanded by
1762 your shell. Globbing makes Wget look for a directory listing, which is
1763 system-specific. This is why it currently works only with Unix @sc{ftp}
1764 servers (and the ones emulating Unix @code{ls} output).
1767 @item --no-passive-ftp
1768 Disable the use of the @dfn{passive} FTP transfer mode. Passive FTP
1769 mandates that the client connect to the server to establish the data
1770 connection rather than the other way around.
1772 If the machine is connected to the Internet directly, both passive and
1773 active FTP should work equally well. Behind most firewall and NAT
1774 configurations passive FTP has a better chance of working. However,
1775 in some rare firewall configurations, active FTP actually works when
1776 passive FTP doesn't. If you suspect this to be the case, use this
1777 option, or set @code{passive_ftp=off} in your init file.
1779 @cindex symbolic links, retrieving
1780 @item --retr-symlinks
1781 Usually, when retrieving @sc{ftp} directories recursively and a symbolic
1782 link is encountered, the linked-to file is not downloaded. Instead, a
1783 matching symbolic link is created on the local filesystem. The
1784 pointed-to file will not be downloaded unless this recursive retrieval
1785 would have encountered it separately and downloaded it anyway.
1787 When @samp{--retr-symlinks} is specified, however, symbolic links are
1788 traversed and the pointed-to files are retrieved. At this time, this
1789 option does not cause Wget to traverse symlinks to directories and
1790 recurse through them, but in the future it should be enhanced to do
1793 Note that when retrieving a file (not a directory) because it was
1794 specified on the command-line, rather than because it was recursed to,
1795 this option has no effect. Symbolic links are always traversed in this
1799 @node Recursive Retrieval Options, Recursive Accept/Reject Options, FTP Options, Invoking
1800 @section Recursive Retrieval Options
1805 Turn on recursive retrieving. @xref{Recursive Download}, for more
1806 details. The default maximum depth is 5.
1808 @item -l @var{depth}
1809 @itemx --level=@var{depth}
1810 Specify recursion maximum depth level @var{depth} (@pxref{Recursive
1813 @cindex proxy filling
1814 @cindex delete after retrieval
1815 @cindex filling proxy cache
1816 @item --delete-after
1817 This option tells Wget to delete every single file it downloads,
1818 @emph{after} having done so. It is useful for pre-fetching popular
1819 pages through a proxy, e.g.:
1822 wget -r -nd --delete-after http://whatever.com/~popular/page/
1825 The @samp{-r} option is to retrieve recursively, and @samp{-nd} to not
1828 Note that @samp{--delete-after} deletes files on the local machine. It
1829 does not issue the @samp{DELE} command to remote FTP sites, for
1830 instance. Also note that when @samp{--delete-after} is specified,
1831 @samp{--convert-links} is ignored, so @samp{.orig} files are simply not
1832 created in the first place.
1834 @cindex conversion of links
1835 @cindex link conversion
1837 @itemx --convert-links
1838 After the download is complete, convert the links in the document to
1839 make them suitable for local viewing. This affects not only the visible
1840 hyperlinks, but any part of the document that links to external content,
1841 such as embedded images, links to style sheets, hyperlinks to non-@sc{html}
1844 Each link will be changed in one of the two ways:
1848 The links to files that have been downloaded by Wget will be changed to
1849 refer to the file they point to as a relative link.
1851 Example: if the downloaded file @file{/foo/doc.html} links to
1852 @file{/bar/img.gif}, also downloaded, then the link in @file{doc.html}
1853 will be modified to point to @samp{../bar/img.gif}. This kind of
1854 transformation works reliably for arbitrary combinations of directories.
1857 The links to files that have not been downloaded by Wget will be changed
1858 to include host name and absolute path of the location they point to.
1860 Example: if the downloaded file @file{/foo/doc.html} links to
1861 @file{/bar/img.gif} (or to @file{../bar/img.gif}), then the link in
1862 @file{doc.html} will be modified to point to
1863 @file{http://@var{hostname}/bar/img.gif}.
1866 Because of this, local browsing works reliably: if a linked file was
1867 downloaded, the link will refer to its local name; if it was not
1868 downloaded, the link will refer to its full Internet address rather than
1869 presenting a broken link. The fact that the former links are converted
1870 to relative links ensures that you can move the downloaded hierarchy to
1873 Note that only at the end of the download can Wget know which links have
1874 been downloaded. Because of that, the work done by @samp{-k} will be
1875 performed at the end of all the downloads.
1877 @cindex backing up converted files
1879 @itemx --backup-converted
1880 When converting a file, back up the original version with a @samp{.orig}
1881 suffix. Affects the behavior of @samp{-N} (@pxref{HTTP Time-Stamping
1886 Turn on options suitable for mirroring. This option turns on recursion
1887 and time-stamping, sets infinite recursion depth and keeps @sc{ftp}
1888 directory listings. It is currently equivalent to
1889 @samp{-r -N -l inf --no-remove-listing}.
1891 @cindex page requisites
1892 @cindex required images, downloading
1894 @itemx --page-requisites
1895 This option causes Wget to download all the files that are necessary to
1896 properly display a given @sc{html} page. This includes such things as
1897 inlined images, sounds, and referenced stylesheets.
1899 Ordinarily, when downloading a single @sc{html} page, any requisite documents
1900 that may be needed to display it properly are not downloaded. Using
1901 @samp{-r} together with @samp{-l} can help, but since Wget does not
1902 ordinarily distinguish between external and inlined documents, one is
1903 generally left with ``leaf documents'' that are missing their
1906 For instance, say document @file{1.html} contains an @code{<IMG>} tag
1907 referencing @file{1.gif} and an @code{<A>} tag pointing to external
1908 document @file{2.html}. Say that @file{2.html} is similar but that its
1909 image is @file{2.gif} and it links to @file{3.html}. Say this
1910 continues up to some arbitrarily high number.
1912 If one executes the command:
1915 wget -r -l 2 http://@var{site}/1.html
1918 then @file{1.html}, @file{1.gif}, @file{2.html}, @file{2.gif}, and
1919 @file{3.html} will be downloaded. As you can see, @file{3.html} is
1920 without its requisite @file{3.gif} because Wget is simply counting the
1921 number of hops (up to 2) away from @file{1.html} in order to determine
1922 where to stop the recursion. However, with this command:
1925 wget -r -l 2 -p http://@var{site}/1.html
1928 all the above files @emph{and} @file{3.html}'s requisite @file{3.gif}
1929 will be downloaded. Similarly,
1932 wget -r -l 1 -p http://@var{site}/1.html
1935 will cause @file{1.html}, @file{1.gif}, @file{2.html}, and @file{2.gif}
1936 to be downloaded. One might think that:
1939 wget -r -l 0 -p http://@var{site}/1.html
1942 would download just @file{1.html} and @file{1.gif}, but unfortunately
1943 this is not the case, because @samp{-l 0} is equivalent to
1944 @samp{-l inf}---that is, infinite recursion. To download a single @sc{html}
1945 page (or a handful of them, all specified on the command-line or in a
1946 @samp{-i} @sc{url} input file) and its (or their) requisites, simply leave off
1947 @samp{-r} and @samp{-l}:
1950 wget -p http://@var{site}/1.html
1953 Note that Wget will behave as if @samp{-r} had been specified, but only
1954 that single page and its requisites will be downloaded. Links from that
1955 page to external documents will not be followed. Actually, to download
1956 a single page and all its requisites (even if they exist on separate
1957 websites), and make sure the lot displays properly locally, this author
1958 likes to use a few options in addition to @samp{-p}:
1961 wget -E -H -k -K -p http://@var{site}/@var{document}
1964 To finish off this topic, it's worth knowing that Wget's idea of an
1965 external document link is any URL specified in an @code{<A>} tag, an
1966 @code{<AREA>} tag, or a @code{<LINK>} tag other than @code{<LINK
1969 @cindex @sc{html} comments
1970 @cindex comments, @sc{html}
1971 @item --strict-comments
1972 Turn on strict parsing of @sc{html} comments. The default is to terminate
1973 comments at the first occurrence of @samp{-->}.
1975 According to specifications, @sc{html} comments are expressed as @sc{sgml}
1976 @dfn{declarations}. Declaration is special markup that begins with
1977 @samp{<!} and ends with @samp{>}, such as @samp{<!DOCTYPE ...>}, that
1978 may contain comments between a pair of @samp{--} delimiters. @sc{html}
1979 comments are ``empty declarations'', @sc{sgml} declarations without any
1980 non-comment text. Therefore, @samp{<!--foo-->} is a valid comment, and
1981 so is @samp{<!--one-- --two-->}, but @samp{<!--1--2-->} is not.
1983 On the other hand, most @sc{html} writers don't perceive comments as anything
1984 other than text delimited with @samp{<!--} and @samp{-->}, which is not
1985 quite the same. For example, something like @samp{<!------------>}
1986 works as a valid comment as long as the number of dashes is a multiple
1987 of four (!). If not, the comment technically lasts until the next
1988 @samp{--}, which may be at the other end of the document. Because of
1989 this, many popular browsers completely ignore the specification and
1990 implement what users have come to expect: comments delimited with
1991 @samp{<!--} and @samp{-->}.
1993 Until version 1.9, Wget interpreted comments strictly, which resulted in
1994 missing links in many web pages that displayed fine in browsers, but had
1995 the misfortune of containing non-compliant comments. Beginning with
1996 version 1.9, Wget has joined the ranks of clients that implements
1997 ``naive'' comments, terminating each comment at the first occurrence of
2000 If, for whatever reason, you want strict comment parsing, use this
2001 option to turn it on.
2004 @node Recursive Accept/Reject Options, Exit Status, Recursive Retrieval Options, Invoking
2005 @section Recursive Accept/Reject Options
2008 @item -A @var{acclist} --accept @var{acclist}
2009 @itemx -R @var{rejlist} --reject @var{rejlist}
2010 Specify comma-separated lists of file name suffixes or patterns to
2011 accept or reject (@pxref{Types of Files}). Note that if
2012 any of the wildcard characters, @samp{*}, @samp{?}, @samp{[} or
2013 @samp{]}, appear in an element of @var{acclist} or @var{rejlist},
2014 it will be treated as a pattern, rather than a suffix.
2016 @item -D @var{domain-list}
2017 @itemx --domains=@var{domain-list}
2018 Set domains to be followed. @var{domain-list} is a comma-separated list
2019 of domains. Note that it does @emph{not} turn on @samp{-H}.
2021 @item --exclude-domains @var{domain-list}
2022 Specify the domains that are @emph{not} to be followed
2023 (@pxref{Spanning Hosts}).
2025 @cindex follow FTP links
2027 Follow @sc{ftp} links from @sc{html} documents. Without this option,
2028 Wget will ignore all the @sc{ftp} links.
2030 @cindex tag-based recursive pruning
2031 @item --follow-tags=@var{list}
2032 Wget has an internal table of @sc{html} tag / attribute pairs that it
2033 considers when looking for linked documents during a recursive
2034 retrieval. If a user wants only a subset of those tags to be
2035 considered, however, he or she should be specify such tags in a
2036 comma-separated @var{list} with this option.
2038 @item --ignore-tags=@var{list}
2039 This is the opposite of the @samp{--follow-tags} option. To skip
2040 certain @sc{html} tags when recursively looking for documents to download,
2041 specify them in a comma-separated @var{list}.
2043 In the past, this option was the best bet for downloading a single page
2044 and its requisites, using a command-line like:
2047 wget --ignore-tags=a,area -H -k -K -r http://@var{site}/@var{document}
2050 However, the author of this option came across a page with tags like
2051 @code{<LINK REL="home" HREF="/">} and came to the realization that
2052 specifying tags to ignore was not enough. One can't just tell Wget to
2053 ignore @code{<LINK>}, because then stylesheets will not be downloaded.
2054 Now the best bet for downloading a single page and its requisites is the
2055 dedicated @samp{--page-requisites} option.
2060 Ignore case when matching files and directories. This influences the
2061 behavior of -R, -A, -I, and -X options, as well as globbing
2062 implemented when downloading from FTP sites. For example, with this
2063 option, @samp{-A *.txt} will match @samp{file1.txt}, but also
2064 @samp{file2.TXT}, @samp{file3.TxT}, and so on.
2068 Enable spanning across hosts when doing recursive retrieving
2069 (@pxref{Spanning Hosts}).
2073 Follow relative links only. Useful for retrieving a specific home page
2074 without any distractions, not even those from the same hosts
2075 (@pxref{Relative Links}).
2078 @itemx --include-directories=@var{list}
2079 Specify a comma-separated list of directories you wish to follow when
2080 downloading (@pxref{Directory-Based Limits}). Elements
2081 of @var{list} may contain wildcards.
2084 @itemx --exclude-directories=@var{list}
2085 Specify a comma-separated list of directories you wish to exclude from
2086 download (@pxref{Directory-Based Limits}). Elements of
2087 @var{list} may contain wildcards.
2091 Do not ever ascend to the parent directory when retrieving recursively.
2092 This is a useful option, since it guarantees that only the files
2093 @emph{below} a certain hierarchy will be downloaded.
2094 @xref{Directory-Based Limits}, for more details.
2099 @node Exit Status, , Recursive Accept/Reject Options, Invoking
2100 @section Exit Status
2102 @c man begin EXITSTATUS
2104 Wget may return one of several error codes if it encounters problems.
2109 No problems occurred.
2115 Parse error---for instance, when parsing command-line options, the
2116 @samp{.wgetrc} or @samp{.netrc}...
2125 SSL verification failure.
2128 Username/password authentication failure.
2134 Server issued an error response.
2138 With the exceptions of 0 and 1, the lower-numbered exit codes take
2139 precedence over higher-numbered ones, when multiple types of errors
2142 In versions of Wget prior to 1.12, Wget's exit status tended to be
2143 unhelpful and inconsistent. Recursive downloads would virtually always
2144 return 0 (success), regardless of any issues encountered, and
2145 non-recursive fetches only returned the status corresponding to the
2146 most recently-attempted download.
2150 @node Recursive Download, Following Links, Invoking, Top
2151 @chapter Recursive Download
2154 @cindex recursive download
2156 GNU Wget is capable of traversing parts of the Web (or a single
2157 @sc{http} or @sc{ftp} server), following links and directory structure.
2158 We refer to this as to @dfn{recursive retrieval}, or @dfn{recursion}.
2160 With @sc{http} @sc{url}s, Wget retrieves and parses the @sc{html} or
2161 @sc{css} from the given @sc{url}, retrieving the files the document
2162 refers to, through markup like @code{href} or @code{src}, or @sc{css}
2163 @sc{uri} values specified using the @samp{url()} functional notation.
2164 If the freshly downloaded file is also of type @code{text/html},
2165 @code{application/xhtml+xml}, or @code{text/css}, it will be parsed
2166 and followed further.
2168 Recursive retrieval of @sc{http} and @sc{html}/@sc{css} content is
2169 @dfn{breadth-first}. This means that Wget first downloads the requested
2170 document, then the documents linked from that document, then the
2171 documents linked by them, and so on. In other words, Wget first
2172 downloads the documents at depth 1, then those at depth 2, and so on
2173 until the specified maximum depth.
2175 The maximum @dfn{depth} to which the retrieval may descend is specified
2176 with the @samp{-l} option. The default maximum depth is five layers.
2178 When retrieving an @sc{ftp} @sc{url} recursively, Wget will retrieve all
2179 the data from the given directory tree (including the subdirectories up
2180 to the specified depth) on the remote server, creating its mirror image
2181 locally. @sc{ftp} retrieval is also limited by the @code{depth}
2182 parameter. Unlike @sc{http} recursion, @sc{ftp} recursion is performed
2185 By default, Wget will create a local directory tree, corresponding to
2186 the one found on the remote server.
2188 Recursive retrieving can find a number of applications, the most
2189 important of which is mirroring. It is also useful for @sc{www}
2190 presentations, and any other opportunities where slow network
2191 connections should be bypassed by storing the files locally.
2193 You should be warned that recursive downloads can overload the remote
2194 servers. Because of that, many administrators frown upon them and may
2195 ban access from your site if they detect very fast downloads of big
2196 amounts of content. When downloading from Internet servers, consider
2197 using the @samp{-w} option to introduce a delay between accesses to the
2198 server. The download will take a while longer, but the server
2199 administrator will not be alarmed by your rudeness.
2201 Of course, recursive download may cause problems on your machine. If
2202 left to run unchecked, it can easily fill up the disk. If downloading
2203 from local network, it can also take bandwidth on the system, as well as
2204 consume memory and CPU.
2206 Try to specify the criteria that match the kind of download you are
2207 trying to achieve. If you want to download only one page, use
2208 @samp{--page-requisites} without any additional recursion. If you want
2209 to download things under one directory, use @samp{-np} to avoid
2210 downloading things from other directories. If you want to download all
2211 the files from one directory, use @samp{-l 1} to make sure the recursion
2212 depth never exceeds one. @xref{Following Links}, for more information
2215 Recursive retrieval should be used with care. Don't say you were not
2218 @node Following Links, Time-Stamping, Recursive Download, Top
2219 @chapter Following Links
2221 @cindex following links
2223 When retrieving recursively, one does not wish to retrieve loads of
2224 unnecessary data. Most of the time the users bear in mind exactly what
2225 they want to download, and want Wget to follow only specific links.
2227 For example, if you wish to download the music archive from
2228 @samp{fly.srk.fer.hr}, you will not want to download all the home pages
2229 that happen to be referenced by an obscure part of the archive.
2231 Wget possesses several mechanisms that allows you to fine-tune which
2232 links it will follow.
2235 * Spanning Hosts:: (Un)limiting retrieval based on host name.
2236 * Types of Files:: Getting only certain files.
2237 * Directory-Based Limits:: Getting only certain directories.
2238 * Relative Links:: Follow relative links only.
2239 * FTP Links:: Following FTP links.
2242 @node Spanning Hosts, Types of Files, Following Links, Following Links
2243 @section Spanning Hosts
2244 @cindex spanning hosts
2245 @cindex hosts, spanning
2247 Wget's recursive retrieval normally refuses to visit hosts different
2248 than the one you specified on the command line. This is a reasonable
2249 default; without it, every retrieval would have the potential to turn
2250 your Wget into a small version of google.
2252 However, visiting different hosts, or @dfn{host spanning,} is sometimes
2253 a useful option. Maybe the images are served from a different server.
2254 Maybe you're mirroring a site that consists of pages interlinked between
2255 three servers. Maybe the server has two equivalent names, and the @sc{html}
2256 pages refer to both interchangeably.
2259 @item Span to any host---@samp{-H}
2261 The @samp{-H} option turns on host spanning, thus allowing Wget's
2262 recursive run to visit any host referenced by a link. Unless sufficient
2263 recursion-limiting criteria are applied depth, these foreign hosts will
2264 typically link to yet more hosts, and so on until Wget ends up sucking
2265 up much more data than you have intended.
2267 @item Limit spanning to certain domains---@samp{-D}
2269 The @samp{-D} option allows you to specify the domains that will be
2270 followed, thus limiting the recursion only to the hosts that belong to
2271 these domains. Obviously, this makes sense only in conjunction with
2272 @samp{-H}. A typical example would be downloading the contents of
2273 @samp{www.server.com}, but allowing downloads from
2274 @samp{images.server.com}, etc.:
2277 wget -rH -Dserver.com http://www.server.com/
2280 You can specify more than one address by separating them with a comma,
2281 e.g. @samp{-Ddomain1.com,domain2.com}.
2283 @item Keep download off certain domains---@samp{--exclude-domains}
2285 If there are domains you want to exclude specifically, you can do it
2286 with @samp{--exclude-domains}, which accepts the same type of arguments
2287 of @samp{-D}, but will @emph{exclude} all the listed domains. For
2288 example, if you want to download all the hosts from @samp{foo.edu}
2289 domain, with the exception of @samp{sunsite.foo.edu}, you can do it like
2293 wget -rH -Dfoo.edu --exclude-domains sunsite.foo.edu \
2299 @node Types of Files, Directory-Based Limits, Spanning Hosts, Following Links
2300 @section Types of Files
2301 @cindex types of files
2303 When downloading material from the web, you will often want to restrict
2304 the retrieval to only certain file types. For example, if you are
2305 interested in downloading @sc{gif}s, you will not be overjoyed to get
2306 loads of PostScript documents, and vice versa.
2308 Wget offers two options to deal with this problem. Each option
2309 description lists a short name, a long name, and the equivalent command
2312 @cindex accept wildcards
2313 @cindex accept suffixes
2314 @cindex wildcards, accept
2315 @cindex suffixes, accept
2317 @item -A @var{acclist}
2318 @itemx --accept @var{acclist}
2319 @itemx accept = @var{acclist}
2320 @itemx --accept-regex @var{urlregex}
2321 @itemx accept-regex = @var{urlregex}
2322 The argument to @samp{--accept} option is a list of file suffixes or
2323 patterns that Wget will download during recursive retrieval. A suffix
2324 is the ending part of a file, and consists of ``normal'' letters,
2325 e.g. @samp{gif} or @samp{.jpg}. A matching pattern contains shell-like
2326 wildcards, e.g. @samp{books*} or @samp{zelazny*196[0-9]*}.
2328 So, specifying @samp{wget -A gif,jpg} will make Wget download only the
2329 files ending with @samp{gif} or @samp{jpg}, i.e. @sc{gif}s and
2330 @sc{jpeg}s. On the other hand, @samp{wget -A "zelazny*196[0-9]*"} will
2331 download only files beginning with @samp{zelazny} and containing numbers
2332 from 1960 to 1969 anywhere within. Look up the manual of your shell for
2333 a description of how pattern matching works.
2335 Of course, any number of suffixes and patterns can be combined into a
2336 comma-separated list, and given as an argument to @samp{-A}.
2338 The argument to @samp{--accept-regex} option is a regular expression which
2339 is matched against the complete URL.
2341 @cindex reject wildcards
2342 @cindex reject suffixes
2343 @cindex wildcards, reject
2344 @cindex suffixes, reject
2345 @item -R @var{rejlist}
2346 @itemx --reject @var{rejlist}
2347 @itemx reject = @var{rejlist}
2348 @itemx --reject-regex @var{urlregex}
2349 @itemx reject-regex = @var{urlregex}
2350 The @samp{--reject} option works the same way as @samp{--accept}, only
2351 its logic is the reverse; Wget will download all files @emph{except} the
2352 ones matching the suffixes (or patterns) in the list.
2354 So, if you want to download a whole page except for the cumbersome
2355 @sc{mpeg}s and @sc{.au} files, you can use @samp{wget -R mpg,mpeg,au}.
2356 Analogously, to download all files except the ones beginning with
2357 @samp{bjork}, use @samp{wget -R "bjork*"}. The quotes are to prevent
2358 expansion by the shell.
2361 The argument to @samp{--accept-regex} option is a regular expression which
2362 is matched against the complete URL.
2365 The @samp{-A} and @samp{-R} options may be combined to achieve even
2366 better fine-tuning of which files to retrieve. E.g. @samp{wget -A
2367 "*zelazny*" -R .ps} will download all the files having @samp{zelazny} as
2368 a part of their name, but @emph{not} the PostScript files.
2370 Note that these two options do not affect the downloading of @sc{html}
2371 files (as determined by a @samp{.htm} or @samp{.html} filename
2372 prefix). This behavior may not be desirable for all users, and may be
2373 changed for future versions of Wget.
2375 Note, too, that query strings (strings at the end of a URL beginning
2376 with a question mark (@samp{?}) are not included as part of the
2377 filename for accept/reject rules, even though these will actually
2378 contribute to the name chosen for the local file. It is expected that
2379 a future version of Wget will provide an option to allow matching
2380 against query strings.
2382 Finally, it's worth noting that the accept/reject lists are matched
2383 @emph{twice} against downloaded files: once against the URL's filename
2384 portion, to determine if the file should be downloaded in the first
2385 place; then, after it has been accepted and successfully downloaded,
2386 the local file's name is also checked against the accept/reject lists
2387 to see if it should be removed. The rationale was that, since
2388 @samp{.htm} and @samp{.html} files are always downloaded regardless of
2389 accept/reject rules, they should be removed @emph{after} being
2390 downloaded and scanned for links, if they did match the accept/reject
2391 lists. However, this can lead to unexpected results, since the local
2392 filenames can differ from the original URL filenames in the following
2393 ways, all of which can change whether an accept/reject rule matches:
2397 If the local file already exists and @samp{--no-directories} was
2398 specified, a numeric suffix will be appended to the original name.
2400 If @samp{--adjust-extension} was specified, the local filename might have
2401 @samp{.html} appended to it. If Wget is invoked with @samp{-E -A.php},
2402 a filename such as @samp{index.php} will match be accepted, but upon
2403 download will be named @samp{index.php.html}, which no longer matches,
2404 and so the file will be deleted.
2406 Query strings do not contribute to URL matching, but are included in
2407 local filenames, and so @emph{do} contribute to filename matching.
2411 This behavior, too, is considered less-than-desirable, and may change
2412 in a future version of Wget.
2414 @node Directory-Based Limits, Relative Links, Types of Files, Following Links
2415 @section Directory-Based Limits
2417 @cindex directory limits
2419 Regardless of other link-following facilities, it is often useful to
2420 place the restriction of what files to retrieve based on the directories
2421 those files are placed in. There can be many reasons for this---the
2422 home pages may be organized in a reasonable directory structure; or some
2423 directories may contain useless information, e.g. @file{/cgi-bin} or
2424 @file{/dev} directories.
2426 Wget offers three different options to deal with this requirement. Each
2427 option description lists a short name, a long name, and the equivalent
2428 command in @file{.wgetrc}.
2430 @cindex directories, include
2431 @cindex include directories
2432 @cindex accept directories
2435 @itemx --include @var{list}
2436 @itemx include_directories = @var{list}
2437 @samp{-I} option accepts a comma-separated list of directories included
2438 in the retrieval. Any other directories will simply be ignored. The
2439 directories are absolute paths.
2441 So, if you wish to download from @samp{http://host/people/bozo/}
2442 following only links to bozo's colleagues in the @file{/people}
2443 directory and the bogus scripts in @file{/cgi-bin}, you can specify:
2446 wget -I /people,/cgi-bin http://host/people/bozo/
2449 @cindex directories, exclude
2450 @cindex exclude directories
2451 @cindex reject directories
2453 @itemx --exclude @var{list}
2454 @itemx exclude_directories = @var{list}
2455 @samp{-X} option is exactly the reverse of @samp{-I}---this is a list of
2456 directories @emph{excluded} from the download. E.g. if you do not want
2457 Wget to download things from @file{/cgi-bin} directory, specify @samp{-X
2458 /cgi-bin} on the command line.
2460 The same as with @samp{-A}/@samp{-R}, these two options can be combined
2461 to get a better fine-tuning of downloading subdirectories. E.g. if you
2462 want to load all the files from @file{/pub} hierarchy except for
2463 @file{/pub/worthless}, specify @samp{-I/pub -X/pub/worthless}.
2468 @itemx no_parent = on
2469 The simplest, and often very useful way of limiting directories is
2470 disallowing retrieval of the links that refer to the hierarchy
2471 @dfn{above} than the beginning directory, i.e. disallowing ascent to the
2472 parent directory/directories.
2474 The @samp{--no-parent} option (short @samp{-np}) is useful in this case.
2475 Using it guarantees that you will never leave the existing hierarchy.
2476 Supposing you issue Wget with:
2479 wget -r --no-parent http://somehost/~luzer/my-archive/
2482 You may rest assured that none of the references to
2483 @file{/~his-girls-homepage/} or @file{/~luzer/all-my-mpegs/} will be
2484 followed. Only the archive you are interested in will be downloaded.
2485 Essentially, @samp{--no-parent} is similar to
2486 @samp{-I/~luzer/my-archive}, only it handles redirections in a more
2487 intelligent fashion.
2489 @strong{Note} that, for HTTP (and HTTPS), the trailing slash is very
2490 important to @samp{--no-parent}. HTTP has no concept of a ``directory''---Wget
2491 relies on you to indicate what's a directory and what isn't. In
2492 @samp{http://foo/bar/}, Wget will consider @samp{bar} to be a
2493 directory, while in @samp{http://foo/bar} (no trailing slash),
2494 @samp{bar} will be considered a filename (so @samp{--no-parent} would be
2495 meaningless, as its parent is @samp{/}).
2498 @node Relative Links, FTP Links, Directory-Based Limits, Following Links
2499 @section Relative Links
2500 @cindex relative links
2502 When @samp{-L} is turned on, only the relative links are ever followed.
2503 Relative links are here defined those that do not refer to the web
2504 server root. For example, these links are relative:
2508 <a href="foo/bar.gif">
2509 <a href="../foo/bar.gif">
2512 These links are not relative:
2516 <a href="/foo/bar.gif">
2517 <a href="http://www.server.com/foo/bar.gif">
2520 Using this option guarantees that recursive retrieval will not span
2521 hosts, even without @samp{-H}. In simple cases it also allows downloads
2522 to ``just work'' without having to convert links.
2524 This option is probably not very useful and might be removed in a future
2527 @node FTP Links, , Relative Links, Following Links
2528 @section Following FTP Links
2529 @cindex following ftp links
2531 The rules for @sc{ftp} are somewhat specific, as it is necessary for
2532 them to be. @sc{ftp} links in @sc{html} documents are often included
2533 for purposes of reference, and it is often inconvenient to download them
2536 To have @sc{ftp} links followed from @sc{html} documents, you need to
2537 specify the @samp{--follow-ftp} option. Having done that, @sc{ftp}
2538 links will span hosts regardless of @samp{-H} setting. This is logical,
2539 as @sc{ftp} links rarely point to the same host where the @sc{http}
2540 server resides. For similar reasons, the @samp{-L} options has no
2541 effect on such downloads. On the other hand, domain acceptance
2542 (@samp{-D}) and suffix rules (@samp{-A} and @samp{-R}) apply normally.
2544 Also note that followed links to @sc{ftp} directories will not be
2545 retrieved recursively further.
2547 @node Time-Stamping, Startup File, Following Links, Top
2548 @chapter Time-Stamping
2549 @cindex time-stamping
2550 @cindex timestamping
2551 @cindex updating the archives
2552 @cindex incremental updating
2554 One of the most important aspects of mirroring information from the
2555 Internet is updating your archives.
2557 Downloading the whole archive again and again, just to replace a few
2558 changed files is expensive, both in terms of wasted bandwidth and money,
2559 and the time to do the update. This is why all the mirroring tools
2560 offer the option of incremental updating.
2562 Such an updating mechanism means that the remote server is scanned in
2563 search of @dfn{new} files. Only those new files will be downloaded in
2564 the place of the old ones.
2566 A file is considered new if one of these two conditions are met:
2570 A file of that name does not already exist locally.
2573 A file of that name does exist, but the remote file was modified more
2574 recently than the local file.
2577 To implement this, the program needs to be aware of the time of last
2578 modification of both local and remote files. We call this information the
2579 @dfn{time-stamp} of a file.
2581 The time-stamping in GNU Wget is turned on using @samp{--timestamping}
2582 (@samp{-N}) option, or through @code{timestamping = on} directive in
2583 @file{.wgetrc}. With this option, for each file it intends to download,
2584 Wget will check whether a local file of the same name exists. If it
2585 does, and the remote file is not newer, Wget will not download it.
2587 If the local file does not exist, or the sizes of the files do not
2588 match, Wget will download the remote file no matter what the time-stamps
2592 * Time-Stamping Usage::
2593 * HTTP Time-Stamping Internals::
2594 * FTP Time-Stamping Internals::
2597 @node Time-Stamping Usage, HTTP Time-Stamping Internals, Time-Stamping, Time-Stamping
2598 @section Time-Stamping Usage
2599 @cindex time-stamping usage
2600 @cindex usage, time-stamping
2602 The usage of time-stamping is simple. Say you would like to download a
2603 file so that it keeps its date of modification.
2606 wget -S http://www.gnu.ai.mit.edu/
2609 A simple @code{ls -l} shows that the time stamp on the local file equals
2610 the state of the @code{Last-Modified} header, as returned by the server.
2611 As you can see, the time-stamping info is preserved locally, even
2612 without @samp{-N} (at least for @sc{http}).
2614 Several days later, you would like Wget to check if the remote file has
2615 changed, and download it if it has.
2618 wget -N http://www.gnu.ai.mit.edu/
2621 Wget will ask the server for the last-modified date. If the local file
2622 has the same timestamp as the server, or a newer one, the remote file
2623 will not be re-fetched. However, if the remote file is more recent,
2624 Wget will proceed to fetch it.
2626 The same goes for @sc{ftp}. For example:
2629 wget "ftp://ftp.ifi.uio.no/pub/emacs/gnus/*"
2632 (The quotes around that URL are to prevent the shell from trying to
2633 interpret the @samp{*}.)
2635 After download, a local directory listing will show that the timestamps
2636 match those on the remote server. Reissuing the command with @samp{-N}
2637 will make Wget re-fetch @emph{only} the files that have been modified
2638 since the last download.
2640 If you wished to mirror the GNU archive every week, you would use a
2641 command like the following, weekly:
2644 wget --timestamping -r ftp://ftp.gnu.org/pub/gnu/
2647 Note that time-stamping will only work for files for which the server
2648 gives a timestamp. For @sc{http}, this depends on getting a
2649 @code{Last-Modified} header. For @sc{ftp}, this depends on getting a
2650 directory listing with dates in a format that Wget can parse
2651 (@pxref{FTP Time-Stamping Internals}).
2653 @node HTTP Time-Stamping Internals, FTP Time-Stamping Internals, Time-Stamping Usage, Time-Stamping
2654 @section HTTP Time-Stamping Internals
2655 @cindex http time-stamping
2657 Time-stamping in @sc{http} is implemented by checking of the
2658 @code{Last-Modified} header. If you wish to retrieve the file
2659 @file{foo.html} through @sc{http}, Wget will check whether
2660 @file{foo.html} exists locally. If it doesn't, @file{foo.html} will be
2661 retrieved unconditionally.
2663 If the file does exist locally, Wget will first check its local
2664 time-stamp (similar to the way @code{ls -l} checks it), and then send a
2665 @code{HEAD} request to the remote server, demanding the information on
2668 The @code{Last-Modified} header is examined to find which file was
2669 modified more recently (which makes it ``newer''). If the remote file
2670 is newer, it will be downloaded; if it is older, Wget will give
2671 up.@footnote{As an additional check, Wget will look at the
2672 @code{Content-Length} header, and compare the sizes; if they are not the
2673 same, the remote file will be downloaded no matter what the time-stamp
2676 When @samp{--backup-converted} (@samp{-K}) is specified in conjunction
2677 with @samp{-N}, server file @samp{@var{X}} is compared to local file
2678 @samp{@var{X}.orig}, if extant, rather than being compared to local file
2679 @samp{@var{X}}, which will always differ if it's been converted by
2680 @samp{--convert-links} (@samp{-k}).
2682 Arguably, @sc{http} time-stamping should be implemented using the
2683 @code{If-Modified-Since} request.
2685 @node FTP Time-Stamping Internals, , HTTP Time-Stamping Internals, Time-Stamping
2686 @section FTP Time-Stamping Internals
2687 @cindex ftp time-stamping
2689 In theory, @sc{ftp} time-stamping works much the same as @sc{http}, only
2690 @sc{ftp} has no headers---time-stamps must be ferreted out of directory
2693 If an @sc{ftp} download is recursive or uses globbing, Wget will use the
2694 @sc{ftp} @code{LIST} command to get a file listing for the directory
2695 containing the desired file(s). It will try to analyze the listing,
2696 treating it like Unix @code{ls -l} output, extracting the time-stamps.
2697 The rest is exactly the same as for @sc{http}. Note that when
2698 retrieving individual files from an @sc{ftp} server without using
2699 globbing or recursion, listing files will not be downloaded (and thus
2700 files will not be time-stamped) unless @samp{-N} is specified.
2702 Assumption that every directory listing is a Unix-style listing may
2703 sound extremely constraining, but in practice it is not, as many
2704 non-Unix @sc{ftp} servers use the Unixoid listing format because most
2705 (all?) of the clients understand it. Bear in mind that @sc{rfc959}
2706 defines no standard way to get a file list, let alone the time-stamps.
2707 We can only hope that a future standard will define this.
2709 Another non-standard solution includes the use of @code{MDTM} command
2710 that is supported by some @sc{ftp} servers (including the popular
2711 @code{wu-ftpd}), which returns the exact time of the specified file.
2712 Wget may support this command in the future.
2714 @node Startup File, Examples, Time-Stamping, Top
2715 @chapter Startup File
2716 @cindex startup file
2722 Once you know how to change default settings of Wget through command
2723 line arguments, you may wish to make some of those settings permanent.
2724 You can do that in a convenient way by creating the Wget startup
2725 file---@file{.wgetrc}.
2727 Besides @file{.wgetrc} is the ``main'' initialization file, it is
2728 convenient to have a special facility for storing passwords. Thus Wget
2729 reads and interprets the contents of @file{$HOME/.netrc}, if it finds
2730 it. You can find @file{.netrc} format in your system manuals.
2732 Wget reads @file{.wgetrc} upon startup, recognizing a limited set of
2736 * Wgetrc Location:: Location of various wgetrc files.
2737 * Wgetrc Syntax:: Syntax of wgetrc.
2738 * Wgetrc Commands:: List of available commands.
2739 * Sample Wgetrc:: A wgetrc example.
2742 @node Wgetrc Location, Wgetrc Syntax, Startup File, Startup File
2743 @section Wgetrc Location
2744 @cindex wgetrc location
2745 @cindex location of wgetrc
2747 When initializing, Wget will look for a @dfn{global} startup file,
2748 @file{/usr/local/etc/wgetrc} by default (or some prefix other than
2749 @file{/usr/local}, if Wget was not installed there) and read commands
2750 from there, if it exists.
2752 Then it will look for the user's file. If the environmental variable
2753 @code{WGETRC} is set, Wget will try to load that file. Failing that, no
2754 further attempts will be made.
2756 If @code{WGETRC} is not set, Wget will try to load @file{$HOME/.wgetrc}.
2758 The fact that user's settings are loaded after the system-wide ones
2759 means that in case of collision user's wgetrc @emph{overrides} the
2760 system-wide wgetrc (in @file{/usr/local/etc/wgetrc} by default).
2761 Fascist admins, away!
2763 @node Wgetrc Syntax, Wgetrc Commands, Wgetrc Location, Startup File
2764 @section Wgetrc Syntax
2765 @cindex wgetrc syntax
2766 @cindex syntax of wgetrc
2768 The syntax of a wgetrc command is simple:
2774 The @dfn{variable} will also be called @dfn{command}. Valid
2775 @dfn{values} are different for different commands.
2777 The commands are case-insensitive and underscore-insensitive. Thus
2778 @samp{DIr__PrefiX} is the same as @samp{dirprefix}. Empty lines, lines
2779 beginning with @samp{#} and lines containing white-space only are
2782 Commands that expect a comma-separated list will clear the list on an
2783 empty command. So, if you wish to reset the rejection list specified in
2784 global @file{wgetrc}, you can do it with:
2790 @node Wgetrc Commands, Sample Wgetrc, Wgetrc Syntax, Startup File
2791 @section Wgetrc Commands
2792 @cindex wgetrc commands
2794 The complete set of commands is listed below. Legal values are listed
2795 after the @samp{=}. Simple Boolean values can be set or unset using
2796 @samp{on} and @samp{off} or @samp{1} and @samp{0}.
2798 Some commands take pseudo-arbitrary values. @var{address} values can be
2799 hostnames or dotted-quad IP addresses. @var{n} can be any positive
2800 integer, or @samp{inf} for infinity, where appropriate. @var{string}
2801 values can be any non-empty string.
2803 Most of these commands have direct command-line equivalents. Also, any
2804 wgetrc command can be specified on the command line using the
2805 @samp{--execute} switch (@pxref{Basic Startup Options}.)
2808 @item accept/reject = @var{string}
2809 Same as @samp{-A}/@samp{-R} (@pxref{Types of Files}).
2811 @item add_hostdir = on/off
2812 Enable/disable host-prefixed file names. @samp{-nH} disables it.
2814 @item ask_password = on/off
2815 Prompt for a password for each connection established. Cannot be specified
2816 when @samp{--password} is being used, because they are mutually
2817 exclusive. Equivalent to @samp{--ask-password}.
2819 @item auth_no_challenge = on/off
2820 If this option is given, Wget will send Basic HTTP authentication
2821 information (plaintext username and password) for all requests. See
2822 @samp{--auth-no-challenge}.
2824 @item background = on/off
2825 Enable/disable going to background---the same as @samp{-b} (which
2828 @item backup_converted = on/off
2829 Enable/disable saving pre-converted files with the suffix
2830 @samp{.orig}---the same as @samp{-K} (which enables it).
2832 @c @item backups = @var{number}
2833 @c #### Document me!
2835 @item base = @var{string}
2836 Consider relative @sc{url}s in input files (specified via the
2837 @samp{input} command or the @samp{--input-file}/@samp{-i} option,
2838 together with @samp{force_html} or @samp{--force-html})
2839 as being relative to @var{string}---the same as @samp{--base=@var{string}}.
2841 @item bind_address = @var{address}
2842 Bind to @var{address}, like the @samp{--bind-address=@var{address}}.
2844 @item ca_certificate = @var{file}
2845 Set the certificate authority bundle file to @var{file}. The same
2846 as @samp{--ca-certificate=@var{file}}.
2848 @item ca_directory = @var{directory}
2849 Set the directory used for certificate authorities. The same as
2850 @samp{--ca-directory=@var{directory}}.
2852 @item cache = on/off
2853 When set to off, disallow server-caching. See the @samp{--no-cache}
2856 @item certificate = @var{file}
2857 Set the client certificate file name to @var{file}. The same as
2858 @samp{--certificate=@var{file}}.
2860 @item certificate_type = @var{string}
2861 Specify the type of the client certificate, legal values being
2862 @samp{PEM} (the default) and @samp{DER} (aka ASN1). The same as
2863 @samp{--certificate-type=@var{string}}.
2865 @item check_certificate = on/off
2866 If this is set to off, the server certificate is not checked against
2867 the specified client authorities. The default is ``on''. The same as
2868 @samp{--check-certificate}.
2870 @item connect_timeout = @var{n}
2871 Set the connect timeout---the same as @samp{--connect-timeout}.
2873 @item content_disposition = on/off
2874 Turn on recognition of the (non-standard) @samp{Content-Disposition}
2875 HTTP header---if set to @samp{on}, the same as @samp{--content-disposition}.
2877 @item trust_server_names = on/off
2878 If set to on, use the last component of a redirection URL for the local
2881 @item continue = on/off
2882 If set to on, force continuation of preexistent partially retrieved
2883 files. See @samp{-c} before setting it.
2885 @item convert_links = on/off
2886 Convert non-relative links locally. The same as @samp{-k}.
2888 @item cookies = on/off
2889 When set to off, disallow cookies. See the @samp{--cookies} option.
2891 @item cut_dirs = @var{n}
2892 Ignore @var{n} remote directory components. Equivalent to
2893 @samp{--cut-dirs=@var{n}}.
2895 @item debug = on/off
2896 Debug mode, same as @samp{-d}.
2898 @item default_page = @var{string}
2899 Default page name---the same as @samp{--default-page=@var{string}}.
2901 @item delete_after = on/off
2902 Delete after download---the same as @samp{--delete-after}.
2904 @item dir_prefix = @var{string}
2905 Top of directory tree---the same as @samp{-P @var{string}}.
2907 @item dirstruct = on/off
2908 Turning dirstruct on or off---the same as @samp{-x} or @samp{-nd},
2911 @item dns_cache = on/off
2912 Turn DNS caching on/off. Since DNS caching is on by default, this
2913 option is normally used to turn it off and is equivalent to
2914 @samp{--no-dns-cache}.
2916 @item dns_timeout = @var{n}
2917 Set the DNS timeout---the same as @samp{--dns-timeout}.
2919 @item domains = @var{string}
2920 Same as @samp{-D} (@pxref{Spanning Hosts}).
2922 @item dot_bytes = @var{n}
2923 Specify the number of bytes ``contained'' in a dot, as seen throughout
2924 the retrieval (1024 by default). You can postfix the value with
2925 @samp{k} or @samp{m}, representing kilobytes and megabytes,
2926 respectively. With dot settings you can tailor the dot retrieval to
2927 suit your needs, or you can use the predefined @dfn{styles}
2928 (@pxref{Download Options}).
2930 @item dot_spacing = @var{n}
2931 Specify the number of dots in a single cluster (10 by default).
2933 @item dots_in_line = @var{n}
2934 Specify the number of dots that will be printed in each line throughout
2935 the retrieval (50 by default).
2937 @item egd_file = @var{file}
2938 Use @var{string} as the EGD socket file name. The same as
2939 @samp{--egd-file=@var{file}}.
2941 @item exclude_directories = @var{string}
2942 Specify a comma-separated list of directories you wish to exclude from
2943 download---the same as @samp{-X @var{string}} (@pxref{Directory-Based
2946 @item exclude_domains = @var{string}
2947 Same as @samp{--exclude-domains=@var{string}} (@pxref{Spanning
2950 @item follow_ftp = on/off
2951 Follow @sc{ftp} links from @sc{html} documents---the same as
2952 @samp{--follow-ftp}.
2954 @item follow_tags = @var{string}
2955 Only follow certain @sc{html} tags when doing a recursive retrieval,
2956 just like @samp{--follow-tags=@var{string}}.
2958 @item force_html = on/off
2959 If set to on, force the input filename to be regarded as an @sc{html}
2960 document---the same as @samp{-F}.
2962 @item ftp_password = @var{string}
2963 Set your @sc{ftp} password to @var{string}. Without this setting, the
2964 password defaults to @samp{-wget@@}, which is a useful default for
2965 anonymous @sc{ftp} access.
2967 This command used to be named @code{passwd} prior to Wget 1.10.
2969 @item ftp_proxy = @var{string}
2970 Use @var{string} as @sc{ftp} proxy, instead of the one specified in
2973 @item ftp_user = @var{string}
2974 Set @sc{ftp} user to @var{string}.
2976 This command used to be named @code{login} prior to Wget 1.10.
2979 Turn globbing on/off---the same as @samp{--glob} and @samp{--no-glob}.
2981 @item header = @var{string}
2982 Define a header for HTTP downloads, like using
2983 @samp{--header=@var{string}}.
2985 @item adjust_extension = on/off
2986 Add a @samp{.html} extension to @samp{text/html} or
2987 @samp{application/xhtml+xml} files that lack one, or a @samp{.css}
2988 extension to @samp{text/css} files that lack one, like
2989 @samp{-E}. Previously named @samp{html_extension} (still acceptable,
2992 @item http_keep_alive = on/off
2993 Turn the keep-alive feature on or off (defaults to on). Turning it
2994 off is equivalent to @samp{--no-http-keep-alive}.
2996 @item http_password = @var{string}
2997 Set @sc{http} password, equivalent to
2998 @samp{--http-password=@var{string}}.
3000 @item http_proxy = @var{string}
3001 Use @var{string} as @sc{http} proxy, instead of the one specified in
3004 @item http_user = @var{string}
3005 Set @sc{http} user to @var{string}, equivalent to
3006 @samp{--http-user=@var{string}}.
3008 @item https_proxy = @var{string}
3009 Use @var{string} as @sc{https} proxy, instead of the one specified in
3012 @item ignore_case = on/off
3013 When set to on, match files and directories case insensitively; the
3014 same as @samp{--ignore-case}.
3016 @item ignore_length = on/off
3017 When set to on, ignore @code{Content-Length} header; the same as
3018 @samp{--ignore-length}.
3020 @item ignore_tags = @var{string}
3021 Ignore certain @sc{html} tags when doing a recursive retrieval, like
3022 @samp{--ignore-tags=@var{string}}.
3024 @item include_directories = @var{string}
3025 Specify a comma-separated list of directories you wish to follow when
3026 downloading---the same as @samp{-I @var{string}}.
3029 When set to on, enable internationalized URI (IRI) support; the same as
3032 @item inet4_only = on/off
3033 Force connecting to IPv4 addresses, off by default. You can put this
3034 in the global init file to disable Wget's attempts to resolve and
3035 connect to IPv6 hosts. Available only if Wget was compiled with IPv6
3036 support. The same as @samp{--inet4-only} or @samp{-4}.
3038 @item inet6_only = on/off
3039 Force connecting to IPv6 addresses, off by default. Available only if
3040 Wget was compiled with IPv6 support. The same as @samp{--inet6-only}
3043 @item input = @var{file}
3044 Read the @sc{url}s from @var{string}, like @samp{-i @var{file}}.
3046 @item keep_session_cookies = on/off
3047 When specified, causes @samp{save_cookies = on} to also save session
3048 cookies. See @samp{--keep-session-cookies}.
3050 @item limit_rate = @var{rate}
3051 Limit the download speed to no more than @var{rate} bytes per second.
3052 The same as @samp{--limit-rate=@var{rate}}.
3054 @item load_cookies = @var{file}
3055 Load cookies from @var{file}. See @samp{--load-cookies @var{file}}.
3057 @item local_encoding = @var{encoding}
3058 Force Wget to use @var{encoding} as the default system encoding. See
3059 @samp{--local-encoding}.
3061 @item logfile = @var{file}
3062 Set logfile to @var{file}, the same as @samp{-o @var{file}}.
3064 @item max_redirect = @var{number}
3065 Specifies the maximum number of redirections to follow for a resource.
3066 See @samp{--max-redirect=@var{number}}.
3068 @item mirror = on/off
3069 Turn mirroring on/off. The same as @samp{-m}.
3071 @item netrc = on/off
3072 Turn reading netrc on or off.
3074 @item no_clobber = on/off
3077 @item no_parent = on/off
3078 Disallow retrieving outside the directory hierarchy, like
3079 @samp{--no-parent} (@pxref{Directory-Based Limits}).
3081 @item no_proxy = @var{string}
3082 Use @var{string} as the comma-separated list of domains to avoid in
3083 proxy loading, instead of the one specified in environment.
3085 @item output_document = @var{file}
3086 Set the output filename---the same as @samp{-O @var{file}}.
3088 @item page_requisites = on/off
3089 Download all ancillary documents necessary for a single @sc{html} page to
3090 display properly---the same as @samp{-p}.
3092 @item passive_ftp = on/off
3093 Change setting of passive @sc{ftp}, equivalent to the
3094 @samp{--passive-ftp} option.
3096 @itemx password = @var{string}
3097 Specify password @var{string} for both @sc{ftp} and @sc{http} file retrieval.
3098 This command can be overridden using the @samp{ftp_password} and
3099 @samp{http_password} command for @sc{ftp} and @sc{http} respectively.
3101 @item post_data = @var{string}
3102 Use POST as the method for all HTTP requests and send @var{string} in
3103 the request body. The same as @samp{--post-data=@var{string}}.
3105 @item post_file = @var{file}
3106 Use POST as the method for all HTTP requests and send the contents of
3107 @var{file} in the request body. The same as
3108 @samp{--post-file=@var{file}}.
3110 @item prefer_family = none/IPv4/IPv6
3111 When given a choice of several addresses, connect to the addresses
3112 with specified address family first. The address order returned by
3113 DNS is used without change by default. The same as @samp{--prefer-family},
3114 which see for a detailed discussion of why this is useful.
3116 @item private_key = @var{file}
3117 Set the private key file to @var{file}. The same as
3118 @samp{--private-key=@var{file}}.
3120 @item private_key_type = @var{string}
3121 Specify the type of the private key, legal values being @samp{PEM}
3122 (the default) and @samp{DER} (aka ASN1). The same as
3123 @samp{--private-type=@var{string}}.
3125 @item progress = @var{string}
3126 Set the type of the progress indicator. Legal types are @samp{dot}
3127 and @samp{bar}. Equivalent to @samp{--progress=@var{string}}.
3129 @item protocol_directories = on/off
3130 When set, use the protocol name as a directory component of local file
3131 names. The same as @samp{--protocol-directories}.
3133 @item proxy_password = @var{string}
3134 Set proxy authentication password to @var{string}, like
3135 @samp{--proxy-password=@var{string}}.
3137 @item proxy_user = @var{string}
3138 Set proxy authentication user name to @var{string}, like
3139 @samp{--proxy-user=@var{string}}.
3141 @item quiet = on/off
3142 Quiet mode---the same as @samp{-q}.
3144 @item quota = @var{quota}
3145 Specify the download quota, which is useful to put in the global
3146 @file{wgetrc}. When download quota is specified, Wget will stop
3147 retrieving after the download sum has become greater than quota. The
3148 quota can be specified in bytes (default), kbytes @samp{k} appended) or
3149 mbytes (@samp{m} appended). Thus @samp{quota = 5m} will set the quota
3150 to 5 megabytes. Note that the user's startup file overrides system
3153 @item random_file = @var{file}
3154 Use @var{file} as a source of randomness on systems lacking
3157 @item random_wait = on/off
3158 Turn random between-request wait times on or off. The same as
3159 @samp{--random-wait}.
3161 @item read_timeout = @var{n}
3162 Set the read (and write) timeout---the same as
3163 @samp{--read-timeout=@var{n}}.
3165 @item reclevel = @var{n}
3166 Recursion level (depth)---the same as @samp{-l @var{n}}.
3168 @item recursive = on/off
3169 Recursive on/off---the same as @samp{-r}.
3171 @item referer = @var{string}
3172 Set HTTP @samp{Referer:} header just like
3173 @samp{--referer=@var{string}}. (Note that it was the folks who wrote
3174 the @sc{http} spec who got the spelling of ``referrer'' wrong.)
3176 @item relative_only = on/off
3177 Follow only relative links---the same as @samp{-L} (@pxref{Relative
3180 @item remote_encoding = @var{encoding}
3181 Force Wget to use @var{encoding} as the default remote server encoding.
3182 See @samp{--remote-encoding}.
3184 @item remove_listing = on/off
3185 If set to on, remove @sc{ftp} listings downloaded by Wget. Setting it
3186 to off is the same as @samp{--no-remove-listing}.
3188 @item restrict_file_names = unix/windows
3189 Restrict the file names generated by Wget from URLs. See
3190 @samp{--restrict-file-names} for a more detailed description.
3192 @item retr_symlinks = on/off
3193 When set to on, retrieve symbolic links as if they were plain files; the
3194 same as @samp{--retr-symlinks}.
3196 @item retry_connrefused = on/off
3197 When set to on, consider ``connection refused'' a transient
3198 error---the same as @samp{--retry-connrefused}.
3200 @item robots = on/off
3201 Specify whether the norobots convention is respected by Wget, ``on'' by
3202 default. This switch controls both the @file{/robots.txt} and the
3203 @samp{nofollow} aspect of the spec. @xref{Robot Exclusion}, for more
3204 details about this. Be sure you know what you are doing before turning
3207 @item save_cookies = @var{file}
3208 Save cookies to @var{file}. The same as @samp{--save-cookies
3211 @item save_headers = on/off
3212 Same as @samp{--save-headers}.
3214 @item secure_protocol = @var{string}
3215 Choose the secure protocol to be used. Legal values are @samp{auto}
3216 (the default), @samp{SSLv2}, @samp{SSLv3}, and @samp{TLSv1}. The same
3217 as @samp{--secure-protocol=@var{string}}.
3219 @item server_response = on/off
3220 Choose whether or not to print the @sc{http} and @sc{ftp} server
3221 responses---the same as @samp{-S}.
3223 @item show_all_dns_entries = on/off
3224 When a DNS name is resolved, show all the IP addresses, not just the first
3227 @item span_hosts = on/off
3230 @item spider = on/off
3231 Same as @samp{--spider}.
3233 @item strict_comments = on/off
3234 Same as @samp{--strict-comments}.
3236 @item timeout = @var{n}
3237 Set all applicable timeout values to @var{n}, the same as @samp{-T
3240 @item timestamping = on/off
3241 Turn timestamping on/off. The same as @samp{-N} (@pxref{Time-Stamping}).
3243 @item use_server_timestamps = on/off
3244 If set to @samp{off}, Wget won't set the local file's timestamp by the
3245 one on the server (same as @samp{--no-use-server-timestamps}).
3247 @item tries = @var{n}
3248 Set number of retries per @sc{url}---the same as @samp{-t @var{n}}.
3250 @item use_proxy = on/off
3251 When set to off, don't use proxy even when proxy-related environment
3252 variables are set. In that case it is the same as using
3255 @item user = @var{string}
3256 Specify username @var{string} for both @sc{ftp} and @sc{http} file retrieval.
3257 This command can be overridden using the @samp{ftp_user} and
3258 @samp{http_user} command for @sc{ftp} and @sc{http} respectively.
3260 @item user_agent = @var{string}
3261 User agent identification sent to the HTTP Server---the same as
3262 @samp{--user-agent=@var{string}}.
3264 @item verbose = on/off
3265 Turn verbose on/off---the same as @samp{-v}/@samp{-nv}.
3267 @item wait = @var{n}
3268 Wait @var{n} seconds between retrievals---the same as @samp{-w
3271 @item wait_retry = @var{n}
3272 Wait up to @var{n} seconds between retries of failed retrievals
3273 only---the same as @samp{--waitretry=@var{n}}. Note that this is
3274 turned on by default in the global @file{wgetrc}.
3277 @node Sample Wgetrc, , Wgetrc Commands, Startup File
3278 @section Sample Wgetrc
3279 @cindex sample wgetrc
3281 This is the sample initialization file, as given in the distribution.
3282 It is divided in two section---one for global usage (suitable for global
3283 startup file), and one for local usage (suitable for
3284 @file{$HOME/.wgetrc}). Be careful about the things you change.
3286 Note that almost all the lines are commented out. For a command to have
3287 any effect, you must remove the @samp{#} character at the beginning of
3291 @include sample.wgetrc.munged_for_texi_inclusion
3294 @node Examples, Various, Startup File, Top
3298 @c man begin EXAMPLES
3299 The examples are divided into three sections loosely based on their
3303 * Simple Usage:: Simple, basic usage of the program.
3304 * Advanced Usage:: Advanced tips.
3305 * Very Advanced Usage:: The hairy stuff.
3308 @node Simple Usage, Advanced Usage, Examples, Examples
3309 @section Simple Usage
3313 Say you want to download a @sc{url}. Just type:
3316 wget http://fly.srk.fer.hr/
3320 But what will happen if the connection is slow, and the file is lengthy?
3321 The connection will probably fail before the whole file is retrieved,
3322 more than once. In this case, Wget will try getting the file until it
3323 either gets the whole of it, or exceeds the default number of retries
3324 (this being 20). It is easy to change the number of tries to 45, to
3325 insure that the whole file will arrive safely:
3328 wget --tries=45 http://fly.srk.fer.hr/jpg/flyweb.jpg
3332 Now let's leave Wget to work in the background, and write its progress
3333 to log file @file{log}. It is tiring to type @samp{--tries}, so we
3334 shall use @samp{-t}.
3337 wget -t 45 -o log http://fly.srk.fer.hr/jpg/flyweb.jpg &
3340 The ampersand at the end of the line makes sure that Wget works in the
3341 background. To unlimit the number of retries, use @samp{-t inf}.
3344 The usage of @sc{ftp} is as simple. Wget will take care of login and
3348 wget ftp://gnjilux.srk.fer.hr/welcome.msg
3352 If you specify a directory, Wget will retrieve the directory listing,
3353 parse it and convert it to @sc{html}. Try:
3356 wget ftp://ftp.gnu.org/pub/gnu/
3361 @node Advanced Usage, Very Advanced Usage, Simple Usage, Examples
3362 @section Advanced Usage
3366 You have a file that contains the URLs you want to download? Use the
3373 If you specify @samp{-} as file name, the @sc{url}s will be read from
3377 Create a five levels deep mirror image of the GNU web site, with the
3378 same directory structure the original has, with only one try per
3379 document, saving the log of the activities to @file{gnulog}:
3382 wget -r http://www.gnu.org/ -o gnulog
3386 The same as the above, but convert the links in the downloaded files to
3387 point to local files, so you can view the documents off-line:
3390 wget --convert-links -r http://www.gnu.org/ -o gnulog
3394 Retrieve only one @sc{html} page, but make sure that all the elements needed
3395 for the page to be displayed, such as inline images and external style
3396 sheets, are also downloaded. Also make sure the downloaded page
3397 references the downloaded links.
3400 wget -p --convert-links http://www.server.com/dir/page.html
3403 The @sc{html} page will be saved to @file{www.server.com/dir/page.html}, and
3404 the images, stylesheets, etc., somewhere under @file{www.server.com/},
3405 depending on where they were on the remote server.
3408 The same as the above, but without the @file{www.server.com/} directory.
3409 In fact, I don't want to have all those random server directories
3410 anyway---just save @emph{all} those files under a @file{download/}
3411 subdirectory of the current directory.
3414 wget -p --convert-links -nH -nd -Pdownload \
3415 http://www.server.com/dir/page.html
3419 Retrieve the index.html of @samp{www.lycos.com}, showing the original
3423 wget -S http://www.lycos.com/
3427 Save the server headers with the file, perhaps for post-processing.
3430 wget --save-headers http://www.lycos.com/
3435 Retrieve the first two levels of @samp{wuarchive.wustl.edu}, saving them
3439 wget -r -l2 -P/tmp ftp://wuarchive.wustl.edu/
3443 You want to download all the @sc{gif}s from a directory on an @sc{http}
3444 server. You tried @samp{wget http://www.server.com/dir/*.gif}, but that
3445 didn't work because @sc{http} retrieval does not support globbing. In
3449 wget -r -l1 --no-parent -A.gif http://www.server.com/dir/
3452 More verbose, but the effect is the same. @samp{-r -l1} means to
3453 retrieve recursively (@pxref{Recursive Download}), with maximum depth
3454 of 1. @samp{--no-parent} means that references to the parent directory
3455 are ignored (@pxref{Directory-Based Limits}), and @samp{-A.gif} means to
3456 download only the @sc{gif} files. @samp{-A "*.gif"} would have worked
3460 Suppose you were in the middle of downloading, when Wget was
3461 interrupted. Now you do not want to clobber the files already present.
3465 wget -nc -r http://www.gnu.org/
3469 If you want to encode your own username and password to @sc{http} or
3470 @sc{ftp}, use the appropriate @sc{url} syntax (@pxref{URL Format}).
3473 wget ftp://hniksic:mypassword@@unix.server.com/.emacs
3476 Note, however, that this usage is not advisable on multi-user systems
3477 because it reveals your password to anyone who looks at the output of
3480 @cindex redirecting output
3482 You would like the output documents to go to standard output instead of
3486 wget -O - http://jagor.srce.hr/ http://www.srce.hr/
3489 You can also combine the two options and make pipelines to retrieve the
3490 documents from remote hotlists:
3493 wget -O - http://cool.list.com/ | wget --force-html -i -
3497 @node Very Advanced Usage, , Advanced Usage, Examples
3498 @section Very Advanced Usage
3503 If you wish Wget to keep a mirror of a page (or @sc{ftp}
3504 subdirectories), use @samp{--mirror} (@samp{-m}), which is the shorthand
3505 for @samp{-r -l inf -N}. You can put Wget in the crontab file asking it
3506 to recheck a site each Sunday:
3510 0 0 * * 0 wget --mirror http://www.gnu.org/ -o /home/me/weeklog
3514 In addition to the above, you want the links to be converted for local
3515 viewing. But, after having read this manual, you know that link
3516 conversion doesn't play well with timestamping, so you also want Wget to
3517 back up the original @sc{html} files before the conversion. Wget invocation
3518 would look like this:
3521 wget --mirror --convert-links --backup-converted \
3522 http://www.gnu.org/ -o /home/me/weeklog
3526 But you've also noticed that local viewing doesn't work all that well
3527 when @sc{html} files are saved under extensions other than @samp{.html},
3528 perhaps because they were served as @file{index.cgi}. So you'd like
3529 Wget to rename all the files served with content-type @samp{text/html}
3530 or @samp{application/xhtml+xml} to @file{@var{name}.html}.
3533 wget --mirror --convert-links --backup-converted \
3534 --html-extension -o /home/me/weeklog \
3538 Or, with less typing:
3541 wget -m -k -K -E http://www.gnu.org/ -o /home/me/weeklog
3546 @node Various, Appendices, Examples, Top
3550 This chapter contains all the stuff that could not fit anywhere else.
3553 * Proxies:: Support for proxy servers.
3554 * Distribution:: Getting the latest version.
3555 * Web Site:: GNU Wget's presence on the World Wide Web.
3556 * Mailing Lists:: Wget mailing list for announcements and discussion.
3557 * Internet Relay Chat:: Wget's presence on IRC.
3558 * Reporting Bugs:: How and where to report bugs.
3559 * Portability:: The systems Wget works on.
3560 * Signals:: Signal-handling performed by Wget.
3563 @node Proxies, Distribution, Various, Various
3567 @dfn{Proxies} are special-purpose @sc{http} servers designed to transfer
3568 data from remote servers to local clients. One typical use of proxies
3569 is lightening network load for users behind a slow connection. This is
3570 achieved by channeling all @sc{http} and @sc{ftp} requests through the
3571 proxy which caches the transferred data. When a cached resource is
3572 requested again, proxy will return the data from cache. Another use for
3573 proxies is for companies that separate (for security reasons) their
3574 internal networks from the rest of Internet. In order to obtain
3575 information from the Web, their users connect and retrieve remote data
3576 using an authorized proxy.
3578 @c man begin ENVIRONMENT
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 @env{http_proxy} and @env{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 @env{http_proxy} and
3593 @env{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 @env{no_proxy} is @samp{.mit.edu}, proxy will not be used to retrieve
3603 In addition to the environment variables, proxy location and settings
3604 may be specified from within Wget itself.
3608 @itemx proxy = on/off
3609 This option and the corresponding command may be used to suppress the
3610 use of proxy, even if the appropriate environment variables are set.
3612 @item http_proxy = @var{URL}
3613 @itemx https_proxy = @var{URL}
3614 @itemx ftp_proxy = @var{URL}
3615 @itemx no_proxy = @var{string}
3616 These startup file variables allow you to override the proxy settings
3617 specified by the environment.
3620 Some proxy servers require authorization to enable you to use them. The
3621 authorization consists of @dfn{username} and @dfn{password}, which must
3622 be sent by Wget. As with @sc{http} authorization, several
3623 authentication schemes exist. For proxy authorization only the
3624 @code{Basic} authentication scheme is currently implemented.
3626 You may specify your username and password either through the proxy
3627 @sc{url} or through the command-line options. Assuming that the
3628 company's proxy is located at @samp{proxy.company.com} at port 8001, a
3629 proxy @sc{url} location containing authorization data might look like
3633 http://hniksic:mypassword@@proxy.company.com:8001/
3636 Alternatively, you may use the @samp{proxy-user} and
3637 @samp{proxy-password} options, and the equivalent @file{.wgetrc}
3638 settings @code{proxy_user} and @code{proxy_password} to set the proxy
3639 username and password.
3641 @node Distribution, Web Site, Proxies, Various
3642 @section Distribution
3643 @cindex latest version
3645 Like all GNU utilities, the latest version of Wget can be found at the
3646 master GNU archive site ftp.gnu.org, and its mirrors. For example,
3647 Wget @value{VERSION} can be found at
3648 @url{ftp://ftp.gnu.org/pub/gnu/wget/wget-@value{VERSION}.tar.gz}
3650 @node Web Site, Mailing Lists, Distribution, Various
3654 The official web site for GNU Wget is at
3655 @url{http://www.gnu.org/software/wget/}. However, most useful
3656 information resides at ``The Wget Wgiki'',
3657 @url{http://wget.addictivecode.org/}.
3659 @node Mailing Lists, Internet Relay Chat, Web Site, Various
3660 @section Mailing Lists
3661 @cindex mailing list
3664 @unnumberedsubsec Primary List
3666 The primary mailinglist for discussion, bug-reports, or questions
3667 about GNU Wget is at @email{bug-wget@@gnu.org}. To subscribe, send an
3668 email to @email{bug-wget-join@@gnu.org}, or visit
3669 @url{http://lists.gnu.org/mailman/listinfo/bug-wget}.
3671 You do not need to subscribe to send a message to the list; however,
3672 please note that unsubscribed messages are moderated, and may take a
3673 while before they hit the list---@strong{usually around a day}. If
3674 you want your message to show up immediately, please subscribe to the
3675 list before posting. Archives for the list may be found at
3676 @url{http://lists.gnu.org/pipermail/bug-wget/}.
3678 An NNTP/Usenettish gateway is also available via
3679 @uref{http://gmane.org/about.php,Gmane}. You can see the Gmane
3681 @url{http://news.gmane.org/gmane.comp.web.wget.general}. Note that the
3682 Gmane archives conveniently include messages from both the current
3683 list, and the previous one. Messages also show up in the Gmane
3684 archives sooner than they do at @url{lists.gnu.org}.
3686 @unnumberedsubsec Bug Notices List
3688 Additionally, there is the @email{wget-notify@@addictivecode.org} mailing
3689 list. This is a non-discussion list that receives bug report
3690 notifications from the bug-tracker. To subscribe to this list,
3691 send an email to @email{wget-notify-join@@addictivecode.org},
3692 or visit @url{http://addictivecode.org/mailman/listinfo/wget-notify}.
3694 @unnumberedsubsec Obsolete Lists
3696 Previously, the mailing list @email{wget@@sunsite.dk} was used as the
3697 main discussion list, and another list,
3698 @email{wget-patches@@sunsite.dk} was used for submitting and
3699 discussing patches to GNU Wget.
3701 Messages from @email{wget@@sunsite.dk} are archived at
3704 @url{http://www.mail-archive.com/wget%40sunsite.dk/} and at
3706 @url{http://news.gmane.org/gmane.comp.web.wget.general} (which also
3707 continues to archive the current list, @email{bug-wget@@gnu.org}).
3710 Messages from @email{wget-patches@@sunsite.dk} are archived at
3713 @url{http://news.gmane.org/gmane.comp.web.wget.patches}.
3716 @node Internet Relay Chat, Reporting Bugs, Mailing Lists, Various
3717 @section Internet Relay Chat
3718 @cindex Internet Relay Chat
3722 In addition to the mailinglists, we also have a support channel set up
3723 via IRC at @code{irc.freenode.org}, @code{#wget}. Come check it out!
3725 @node Reporting Bugs, Portability, Internet Relay Chat, Various
3726 @section Reporting Bugs
3728 @cindex reporting bugs
3732 You are welcome to submit bug reports via the GNU Wget bug tracker (see
3733 @url{http://wget.addictivecode.org/BugTracker}).
3735 Before actually submitting a bug report, please try to follow a few
3740 Please try to ascertain that the behavior you see really is a bug. If
3741 Wget crashes, it's a bug. If Wget does not behave as documented,
3742 it's a bug. If things work strange, but you are not sure about the way
3743 they are supposed to work, it might well be a bug, but you might want to
3744 double-check the documentation and the mailing lists (@pxref{Mailing
3748 Try to repeat the bug in as simple circumstances as possible. E.g. if
3749 Wget crashes while downloading @samp{wget -rl0 -kKE -t5 --no-proxy
3750 http://yoyodyne.com -o /tmp/log}, you should try to see if the crash is
3751 repeatable, and if will occur with a simpler set of options. You might
3752 even try to start the download at the page where the crash occurred to
3753 see if that page somehow triggered the crash.
3755 Also, while I will probably be interested to know the contents of your
3756 @file{.wgetrc} file, just dumping it into the debug message is probably
3757 a bad idea. Instead, you should first try to see if the bug repeats
3758 with @file{.wgetrc} moved out of the way. Only if it turns out that
3759 @file{.wgetrc} settings affect the bug, mail me the relevant parts of
3763 Please start Wget with @samp{-d} option and send us the resulting
3764 output (or relevant parts thereof). If Wget was compiled without
3765 debug support, recompile it---it is @emph{much} easier to trace bugs
3766 with debug support on.
3768 Note: please make sure to remove any potentially sensitive information
3769 from the debug log before sending it to the bug address. The
3770 @code{-d} won't go out of its way to collect sensitive information,
3771 but the log @emph{will} contain a fairly complete transcript of Wget's
3772 communication with the server, which may include passwords and pieces
3773 of downloaded data. Since the bug address is publically archived, you
3774 may assume that all bug reports are visible to the public.
3777 If Wget has crashed, try to run it in a debugger, e.g. @code{gdb `which
3778 wget` core} and type @code{where} to get the backtrace. This may not
3779 work if the system administrator has disabled core files, but it is
3784 @node Portability, Signals, Reporting Bugs, Various
3785 @section Portability
3787 @cindex operating systems
3789 Like all GNU software, Wget works on the GNU system. However, since it
3790 uses GNU Autoconf for building and configuring, and mostly avoids using
3791 ``special'' features of any particular Unix, it should compile (and
3792 work) on all common Unix flavors.
3794 Various Wget versions have been compiled and tested under many kinds of
3795 Unix systems, including GNU/Linux, Solaris, SunOS 4.x, Mac OS X, OSF
3796 (aka Digital Unix or Tru64), Ultrix, *BSD, IRIX, AIX, and others. Some
3797 of those systems are no longer in widespread use and may not be able to
3798 support recent versions of Wget. If Wget fails to compile on your
3799 system, we would like to know about it.
3801 Thanks to kind contributors, this version of Wget compiles and works
3802 on 32-bit Microsoft Windows platforms. It has been compiled
3803 successfully using MS Visual C++ 6.0, Watcom, Borland C, and GCC
3804 compilers. Naturally, it is crippled of some features available on
3805 Unix, but it should work as a substitute for people stuck with
3806 Windows. Note that Windows-specific portions of Wget are not
3807 guaranteed to be supported in the future, although this has been the
3808 case in practice for many years now. All questions and problems in
3809 Windows usage should be reported to Wget mailing list at
3810 @email{wget@@sunsite.dk} where the volunteers who maintain the
3811 Windows-related features might look at them.
3813 Support for building on MS-DOS via DJGPP has been contributed by Gisle
3814 Vanem; a port to VMS is maintained by Steven Schweda, and is available
3815 at @url{http://antinode.org/}.
3817 @node Signals, , Portability, Various
3819 @cindex signal handling
3822 Since the purpose of Wget is background work, it catches the hangup
3823 signal (@code{SIGHUP}) and ignores it. If the output was on standard
3824 output, it will be redirected to a file named @file{wget-log}.
3825 Otherwise, @code{SIGHUP} is ignored. This is convenient when you wish
3826 to redirect the output of Wget after having started it.
3829 $ wget http://www.gnus.org/dist/gnus.tar.gz &
3832 SIGHUP received, redirecting output to `wget-log'.
3835 Other than that, Wget will not try to interfere with signals in any way.
3836 @kbd{C-c}, @code{kill -TERM} and @code{kill -KILL} should kill it alike.
3838 @node Appendices, Copying this manual, Various, Top
3841 This chapter contains some references I consider useful.
3844 * Robot Exclusion:: Wget's support for RES.
3845 * Security Considerations:: Security with Wget.
3846 * Contributors:: People who helped.
3849 @node Robot Exclusion, Security Considerations, Appendices, Appendices
3850 @section Robot Exclusion
3851 @cindex robot exclusion
3853 @cindex server maintenance
3855 It is extremely easy to make Wget wander aimlessly around a web site,
3856 sucking all the available data in progress. @samp{wget -r @var{site}},
3857 and you're set. Great? Not for the server admin.
3859 As long as Wget is only retrieving static pages, and doing it at a
3860 reasonable rate (see the @samp{--wait} option), there's not much of a
3861 problem. The trouble is that Wget can't tell the difference between the
3862 smallest static page and the most demanding CGI. A site I know has a
3863 section handled by a CGI Perl script that converts Info files to @sc{html} on
3864 the fly. The script is slow, but works well enough for human users
3865 viewing an occasional Info file. However, when someone's recursive Wget
3866 download stumbles upon the index page that links to all the Info files
3867 through the script, the system is brought to its knees without providing
3868 anything useful to the user (This task of converting Info files could be
3869 done locally and access to Info documentation for all installed GNU
3870 software on a system is available from the @code{info} command).
3872 To avoid this kind of accident, as well as to preserve privacy for
3873 documents that need to be protected from well-behaved robots, the
3874 concept of @dfn{robot exclusion} was invented. The idea is that
3875 the server administrators and document authors can specify which
3876 portions of the site they wish to protect from robots and those
3877 they will permit access.
3879 The most popular mechanism, and the @i{de facto} standard supported by
3880 all the major robots, is the ``Robots Exclusion Standard'' (RES) written
3881 by Martijn Koster et al. in 1994. It specifies the format of a text
3882 file containing directives that instruct the robots which URL paths to
3883 avoid. To be found by the robots, the specifications must be placed in
3884 @file{/robots.txt} in the server root, which the robots are expected to
3887 Although Wget is not a web robot in the strictest sense of the word, it
3888 can download large parts of the site without the user's intervention to
3889 download an individual page. Because of that, Wget honors RES when
3890 downloading recursively. For instance, when you issue:
3893 wget -r http://www.server.com/
3896 First the index of @samp{www.server.com} will be downloaded. If Wget
3897 finds that it wants to download more documents from that server, it will
3898 request @samp{http://www.server.com/robots.txt} and, if found, use it
3899 for further downloads. @file{robots.txt} is loaded only once per each
3902 Until version 1.8, Wget supported the first version of the standard,
3903 written by Martijn Koster in 1994 and available at
3904 @url{http://www.robotstxt.org/wc/norobots.html}. As of version 1.8,
3905 Wget has supported the additional directives specified in the internet
3906 draft @samp{<draft-koster-robots-00.txt>} titled ``A Method for Web
3907 Robots Control''. The draft, which has as far as I know never made to
3908 an @sc{rfc}, is available at
3909 @url{http://www.robotstxt.org/wc/norobots-rfc.txt}.
3911 This manual no longer includes the text of the Robot Exclusion Standard.
3913 The second, less known mechanism, enables the author of an individual
3914 document to specify whether they want the links from the file to be
3915 followed by a robot. This is achieved using the @code{META} tag, like
3919 <meta name="robots" content="nofollow">
3922 This is explained in some detail at
3923 @url{http://www.robotstxt.org/wc/meta-user.html}. Wget supports this
3924 method of robot exclusion in addition to the usual @file{/robots.txt}
3927 If you know what you are doing and really really wish to turn off the
3928 robot exclusion, set the @code{robots} variable to @samp{off} in your
3929 @file{.wgetrc}. You can achieve the same effect from the command line
3930 using the @code{-e} switch, e.g. @samp{wget -e robots=off @var{url}...}.
3932 @node Security Considerations, Contributors, Robot Exclusion, Appendices
3933 @section Security Considerations
3936 When using Wget, you must be aware that it sends unencrypted passwords
3937 through the network, which may present a security problem. Here are the
3938 main issues, and some solutions.
3942 The passwords on the command line are visible using @code{ps}. The best
3943 way around it is to use @code{wget -i -} and feed the @sc{url}s to
3944 Wget's standard input, each on a separate line, terminated by @kbd{C-d}.
3945 Another workaround is to use @file{.netrc} to store passwords; however,
3946 storing unencrypted passwords is also considered a security risk.
3949 Using the insecure @dfn{basic} authentication scheme, unencrypted
3950 passwords are transmitted through the network routers and gateways.
3953 The @sc{ftp} passwords are also in no way encrypted. There is no good
3954 solution for this at the moment.
3957 Although the ``normal'' output of Wget tries to hide the passwords,
3958 debugging logs show them, in all forms. This problem is avoided by
3959 being careful when you send debug logs (yes, even when you send them to
3963 @node Contributors, , Security Considerations, Appendices
3964 @section Contributors
3965 @cindex contributors
3968 GNU Wget was written by Hrvoje Nik@v{s}i@'{c} @email{hniksic@@xemacs.org},
3971 GNU Wget was written by Hrvoje Niksic @email{hniksic@@xemacs.org}.
3974 However, the development of Wget could never have gone as far as it has, were
3975 it not for the help of many people, either with bug reports, feature proposals,
3976 patches, or letters saying ``Thanks!''.
3978 Special thanks goes to the following people (no particular order):
3981 @item Dan Harkless---contributed a lot of code and documentation of
3982 extremely high quality, as well as the @code{--page-requisites} and
3983 related options. He was the principal maintainer for some time and
3986 @item Ian Abbott---contributed bug fixes, Windows-related fixes, and
3987 provided a prototype implementation of the breadth-first recursive
3988 download. Co-maintained Wget during the 1.8 release cycle.
3991 The dotsrc.org crew, in particular Karsten Thygesen---donated system
3992 resources such as the mailing list, web space, @sc{ftp} space, and
3993 version control repositories, along with a lot of time to make these
3994 actually work. Christian Reiniger was of invaluable help with setting
3998 Heiko Herold---provided high-quality Windows builds and contributed
3999 bug and build reports for many years.
4002 Shawn McHorse---bug reports and patches.
4005 Kaveh R. Ghazi---on-the-fly @code{ansi2knr}-ization. Lots of
4009 Gordon Matzigkeit---@file{.netrc} support.
4013 Zlatko @v{C}alu@v{s}i@'{c}, Tomislav Vujec and Dra@v{z}en
4014 Ka@v{c}ar---feature suggestions and ``philosophical'' discussions.
4017 Zlatko Calusic, Tomislav Vujec and Drazen Kacar---feature suggestions
4018 and ``philosophical'' discussions.
4022 Darko Budor---initial port to Windows.
4025 Antonio Rosella---help and suggestions, plus the initial Italian
4030 Tomislav Petrovi@'{c}, Mario Miko@v{c}evi@'{c}---many bug reports and
4034 Tomislav Petrovic, Mario Mikocevic---many bug reports and suggestions.
4039 Fran@,{c}ois Pinard---many thorough bug reports and discussions.
4042 Francois Pinard---many thorough bug reports and discussions.
4046 Karl Eichwalder---lots of help with internationalization, Makefile
4047 layout and many other things.
4050 Junio Hamano---donated support for Opie and @sc{http} @code{Digest}
4054 Mauro Tortonesi---improved IPv6 support, adding support for dual
4055 family systems. Refactored and enhanced FTP IPv6 code. Maintained GNU
4056 Wget from 2004--2007.
4059 Christopher G.@: Lewis---maintenance of the Windows version of GNU WGet.
4062 Gisle Vanem---many helpful patches and improvements, especially for
4063 Windows and MS-DOS support.
4066 Ralf Wildenhues---contributed patches to convert Wget to use Automake as
4067 part of its build process, and various bugfixes.
4070 Steven Schubiger---Many helpful patches, bugfixes and improvements.
4071 Notably, conversion of Wget to use the Gnulib quotes and quoteargs
4072 modules, and the addition of password prompts at the console, via the
4073 Gnulib getpasswd-gnu module.
4076 Ted Mielczarek---donated support for CSS.
4079 Saint Xavier---Support for IRIs (RFC 3987).
4082 People who provided donations for development---including Brian Gough.
4085 The following people have provided patches, bug/build reports, useful
4086 suggestions, beta testing services, fan mail and all the other things
4087 that make maintenance so much fun:
4107 Kristijan @v{C}onka@v{s},
4116 Bertrand Demiddelaer,
4117 Alexander Dergachev,
4130 Aleksandar Erkalovi@'{c},
4133 Aleksandar Erkalovic,
4157 Madhusudan Hosaagrahara,
4161 Erik Magnus Hulthen,
4180 Goran Kezunovi@'{c},
4194 $\Sigma\acute{\iota}\mu o\varsigma\;
4195 \Xi\varepsilon\nu\iota\tau\acute{\epsilon}\lambda\lambda\eta\varsigma$
4196 (Simos KSenitellis),
4205 Nicol@'{a}s Lichtmeier,
4211 Alexander V.@: Lukyanov,
4220 Matthew J.@: Mellon,
4256 @c Texinfo doesn't grok @'{@i}, so we have to use TeX itself.
4258 Juan Jos\'{e} Rodr\'{\i}guez,
4261 Juan Jose Rodriguez,
4263 Maciej W.@: Rozycki,
4270 Steven M.@: Schweda,
4281 Szakacsits Szabolcs,
4296 Douglas E.@: Wegscheid,
4298 Joshua David Williams,
4312 Apologies to all who I accidentally left out, and many thanks to all the
4313 subscribers of the Wget mailing list.
4315 @node Copying this manual, Concept Index, Appendices, Top
4316 @appendix Copying this manual
4319 * GNU Free Documentation License:: Licnse for copying this manual.
4322 @node GNU Free Documentation License, , Copying this manual, Copying this manual
4323 @appendixsec GNU Free Documentation License
4324 @cindex FDL, GNU Free Documentation License
4329 @node Concept Index, , Copying this manual, Top
4330 @unnumbered Concept Index