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 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).
721 If @code{mega} is not enough then you can use the @code{giga}
722 style---each dot represents 1M retrieved, there are eight dots in a
723 cluster, and 32 dots on each line (so each line contains 32M).
725 Note that you can set the default style using the @code{progress}
726 command in @file{.wgetrc}. That setting may be overridden from the
727 command line. The exception is that, when the output is not a TTY, the
728 ``dot'' progress will be favored over ``bar''. To force the bar output,
729 use @samp{--progress=bar:force}.
732 @itemx --timestamping
733 Turn on time-stamping. @xref{Time-Stamping}, for details.
735 @item --no-use-server-timestamps
736 Don't set the local file's timestamp by the one on the server.
738 By default, when a file is downloaded, it's timestamps are set to
739 match those from the remote file. This allows the use of
740 @samp{--timestamping} on subsequent invocations of wget. However, it
741 is sometimes useful to base the local file's timestamp on when it was
742 actually downloaded; for that purpose, the
743 @samp{--no-use-server-timestamps} option has been provided.
745 @cindex server response, print
747 @itemx --server-response
748 Print the headers sent by @sc{http} servers and responses sent by
751 @cindex Wget as spider
754 When invoked with this option, Wget will behave as a Web @dfn{spider},
755 which means that it will not download the pages, just check that they
756 are there. For example, you can use Wget to check your bookmarks:
759 wget --spider --force-html -i bookmarks.html
762 This feature needs much more work for Wget to get close to the
763 functionality of real web spiders.
767 @itemx --timeout=@var{seconds}
768 Set the network timeout to @var{seconds} seconds. This is equivalent
769 to specifying @samp{--dns-timeout}, @samp{--connect-timeout}, and
770 @samp{--read-timeout}, all at the same time.
772 When interacting with the network, Wget can check for timeout and
773 abort the operation if it takes too long. This prevents anomalies
774 like hanging reads and infinite connects. The only timeout enabled by
775 default is a 900-second read timeout. Setting a timeout to 0 disables
776 it altogether. Unless you know what you are doing, it is best not to
777 change the default timeout settings.
779 All timeout-related options accept decimal values, as well as
780 subsecond values. For example, @samp{0.1} seconds is a legal (though
781 unwise) choice of timeout. Subsecond timeouts are useful for checking
782 server response times or for testing network latency.
786 @item --dns-timeout=@var{seconds}
787 Set the DNS lookup timeout to @var{seconds} seconds. DNS lookups that
788 don't complete within the specified time will fail. By default, there
789 is no timeout on DNS lookups, other than that implemented by system
792 @cindex connect timeout
793 @cindex timeout, connect
794 @item --connect-timeout=@var{seconds}
795 Set the connect timeout to @var{seconds} seconds. TCP connections that
796 take longer to establish will be aborted. By default, there is no
797 connect timeout, other than that implemented by system libraries.
800 @cindex timeout, read
801 @item --read-timeout=@var{seconds}
802 Set the read (and write) timeout to @var{seconds} seconds. The
803 ``time'' of this timeout refers to @dfn{idle time}: if, at any point in
804 the download, no data is received for more than the specified number
805 of seconds, reading fails and the download is restarted. This option
806 does not directly affect the duration of the entire download.
808 Of course, the remote server may choose to terminate the connection
809 sooner than this option requires. The default read timeout is 900
812 @cindex bandwidth, limit
814 @cindex limit bandwidth
815 @item --limit-rate=@var{amount}
816 Limit the download speed to @var{amount} bytes per second. Amount may
817 be expressed in bytes, kilobytes with the @samp{k} suffix, or megabytes
818 with the @samp{m} suffix. For example, @samp{--limit-rate=20k} will
819 limit the retrieval rate to 20KB/s. This is useful when, for whatever
820 reason, you don't want Wget to consume the entire available bandwidth.
822 This option allows the use of decimal numbers, usually in conjunction
823 with power suffixes; for example, @samp{--limit-rate=2.5k} is a legal
826 Note that Wget implements the limiting by sleeping the appropriate
827 amount of time after a network read that took less time than specified
828 by the rate. Eventually this strategy causes the TCP transfer to slow
829 down to approximately the specified rate. However, it may take some
830 time for this balance to be achieved, so don't be surprised if limiting
831 the rate doesn't work well with very small files.
835 @item -w @var{seconds}
836 @itemx --wait=@var{seconds}
837 Wait the specified number of seconds between the retrievals. Use of
838 this option is recommended, as it lightens the server load by making the
839 requests less frequent. Instead of in seconds, the time can be
840 specified in minutes using the @code{m} suffix, in hours using @code{h}
841 suffix, or in days using @code{d} suffix.
843 Specifying a large value for this option is useful if the network or the
844 destination host is down, so that Wget can wait long enough to
845 reasonably expect the network error to be fixed before the retry. The
846 waiting interval specified by this function is influenced by
847 @code{--random-wait}, which see.
849 @cindex retries, waiting between
850 @cindex waiting between retries
851 @item --waitretry=@var{seconds}
852 If you don't want Wget to wait between @emph{every} retrieval, but only
853 between retries of failed downloads, you can use this option. Wget will
854 use @dfn{linear backoff}, waiting 1 second after the first failure on a
855 given file, then waiting 2 seconds after the second failure on that
856 file, up to the maximum number of @var{seconds} you specify.
858 By default, Wget will assume a value of 10 seconds.
863 Some web sites may perform log analysis to identify retrieval programs
864 such as Wget by looking for statistically significant similarities in
865 the time between requests. This option causes the time between requests
866 to vary between 0.5 and 1.5 * @var{wait} seconds, where @var{wait} was
867 specified using the @samp{--wait} option, in order to mask Wget's
868 presence from such analysis.
870 A 2001 article in a publication devoted to development on a popular
871 consumer platform provided code to perform this analysis on the fly.
872 Its author suggested blocking at the class C address level to ensure
873 automated retrieval programs were blocked despite changing DHCP-supplied
876 The @samp{--random-wait} option was inspired by this ill-advised
877 recommendation to block many unrelated users from a web site due to the
882 Don't use proxies, even if the appropriate @code{*_proxy} environment
886 For more information about the use of proxies with Wget, @xref{Proxies}.
891 @itemx --quota=@var{quota}
892 Specify download quota for automatic retrievals. The value can be
893 specified in bytes (default), kilobytes (with @samp{k} suffix), or
894 megabytes (with @samp{m} suffix).
896 Note that quota will never affect downloading a single file. So if you
897 specify @samp{wget -Q10k ftp://wuarchive.wustl.edu/ls-lR.gz}, all of the
898 @file{ls-lR.gz} will be downloaded. The same goes even when several
899 @sc{url}s are specified on the command-line. However, quota is
900 respected when retrieving either recursively, or from an input file.
901 Thus you may safely type @samp{wget -Q2m -i sites}---download will be
902 aborted when the quota is exceeded.
904 Setting quota to 0 or to @samp{inf} unlimits the download quota.
907 @cindex caching of DNS lookups
909 Turn off caching of DNS lookups. Normally, Wget remembers the IP
910 addresses it looked up from DNS so it doesn't have to repeatedly
911 contact the DNS server for the same (typically small) set of hosts it
912 retrieves from. This cache exists in memory only; a new Wget run will
915 However, it has been reported that in some situations it is not
916 desirable to cache host names, even for the duration of a
917 short-running application like Wget. With this option Wget issues a
918 new DNS lookup (more precisely, a new call to @code{gethostbyname} or
919 @code{getaddrinfo}) each time it makes a new connection. Please note
920 that this option will @emph{not} affect caching that might be
921 performed by the resolving library or by an external caching layer,
924 If you don't understand exactly what this option does, you probably
927 @cindex file names, restrict
928 @cindex Windows file names
929 @item --restrict-file-names=@var{modes}
930 Change which characters found in remote URLs must be escaped during
931 generation of local filenames. Characters that are @dfn{restricted}
932 by this option are escaped, i.e. replaced with @samp{%HH}, where
933 @samp{HH} is the hexadecimal number that corresponds to the restricted
934 character. This option may also be used to force all alphabetical
935 cases to be either lower- or uppercase.
937 By default, Wget escapes the characters that are not valid or safe as
938 part of file names on your operating system, as well as control
939 characters that are typically unprintable. This option is useful for
940 changing these defaults, perhaps because you are downloading to a
941 non-native partition, or because you want to disable escaping of the
942 control characters, or you want to further restrict characters to only
943 those in the @sc{ascii} range of values.
945 The @var{modes} are a comma-separated set of text values. The
946 acceptable values are @samp{unix}, @samp{windows}, @samp{nocontrol},
947 @samp{ascii}, @samp{lowercase}, and @samp{uppercase}. The values
948 @samp{unix} and @samp{windows} are mutually exclusive (one will
949 override the other), as are @samp{lowercase} and
950 @samp{uppercase}. Those last are special cases, as they do not change
951 the set of characters that would be escaped, but rather force local
952 file paths to be converted either to lower- or uppercase.
954 When ``unix'' is specified, Wget escapes the character @samp{/} and
955 the control characters in the ranges 0--31 and 128--159. This is the
956 default on Unix-like operating systems.
958 When ``windows'' is given, Wget escapes the characters @samp{\},
959 @samp{|}, @samp{/}, @samp{:}, @samp{?}, @samp{"}, @samp{*}, @samp{<},
960 @samp{>}, and the control characters in the ranges 0--31 and 128--159.
961 In addition to this, Wget in Windows mode uses @samp{+} instead of
962 @samp{:} to separate host and port in local file names, and uses
963 @samp{@@} instead of @samp{?} to separate the query portion of the file
964 name from the rest. Therefore, a URL that would be saved as
965 @samp{www.xemacs.org:4300/search.pl?input=blah} in Unix mode would be
966 saved as @samp{www.xemacs.org+4300/search.pl@@input=blah} in Windows
967 mode. This mode is the default on Windows.
969 If you specify @samp{nocontrol}, then the escaping of the control
970 characters is also switched off. This option may make sense
971 when you are downloading URLs whose names contain UTF-8 characters, on
972 a system which can save and display filenames in UTF-8 (some possible
973 byte values used in UTF-8 byte sequences fall in the range of values
974 designated by Wget as ``controls'').
976 The @samp{ascii} mode is used to specify that any bytes whose values
977 are outside the range of @sc{ascii} characters (that is, greater than
978 127) shall be escaped. This can be useful when saving filenames
979 whose encoding does not match the one used locally.
986 Force connecting to IPv4 or IPv6 addresses. With @samp{--inet4-only}
987 or @samp{-4}, Wget will only connect to IPv4 hosts, ignoring AAAA
988 records in DNS, and refusing to connect to IPv6 addresses specified in
989 URLs. Conversely, with @samp{--inet6-only} or @samp{-6}, Wget will
990 only connect to IPv6 hosts and ignore A records and IPv4 addresses.
992 Neither options should be needed normally. By default, an IPv6-aware
993 Wget will use the address family specified by the host's DNS record.
994 If the DNS responds with both IPv4 and IPv6 addresses, Wget will try
995 them in sequence until it finds one it can connect to. (Also see
996 @code{--prefer-family} option described below.)
998 These options can be used to deliberately force the use of IPv4 or
999 IPv6 address families on dual family systems, usually to aid debugging
1000 or to deal with broken network configuration. Only one of
1001 @samp{--inet6-only} and @samp{--inet4-only} may be specified at the
1002 same time. Neither option is available in Wget compiled without IPv6
1005 @item --prefer-family=none/IPv4/IPv6
1006 When given a choice of several addresses, connect to the addresses
1007 with specified address family first. The address order returned by
1008 DNS is used without change by default.
1010 This avoids spurious errors and connect attempts when accessing hosts
1011 that resolve to both IPv6 and IPv4 addresses from IPv4 networks. For
1012 example, @samp{www.kame.net} resolves to
1013 @samp{2001:200:0:8002:203:47ff:fea5:3085} and to
1014 @samp{203.178.141.194}. When the preferred family is @code{IPv4}, the
1015 IPv4 address is used first; when the preferred family is @code{IPv6},
1016 the IPv6 address is used first; if the specified value is @code{none},
1017 the address order returned by DNS is used without change.
1019 Unlike @samp{-4} and @samp{-6}, this option doesn't inhibit access to
1020 any address family, it only changes the @emph{order} in which the
1021 addresses are accessed. Also note that the reordering performed by
1022 this option is @dfn{stable}---it doesn't affect order of addresses of
1023 the same family. That is, the relative order of all IPv4 addresses
1024 and of all IPv6 addresses remains intact in all cases.
1026 @item --retry-connrefused
1027 Consider ``connection refused'' a transient error and try again.
1028 Normally Wget gives up on a URL when it is unable to connect to the
1029 site because failure to connect is taken as a sign that the server is
1030 not running at all and that retries would not help. This option is
1031 for mirroring unreliable sites whose servers tend to disappear for
1032 short periods of time.
1036 @cindex authentication
1037 @item --user=@var{user}
1038 @itemx --password=@var{password}
1039 Specify the username @var{user} and password @var{password} for both
1040 @sc{ftp} and @sc{http} file retrieval. These parameters can be overridden
1041 using the @samp{--ftp-user} and @samp{--ftp-password} options for
1042 @sc{ftp} connections and the @samp{--http-user} and @samp{--http-password}
1043 options for @sc{http} connections.
1045 @item --ask-password
1046 Prompt for a password for each connection established. Cannot be specified
1047 when @samp{--password} is being used, because they are mutually exclusive.
1053 Turn off internationalized URI (IRI) support. Use @samp{--iri} to
1054 turn it on. IRI support is activated by default.
1056 You can set the default state of IRI support using the @code{iri}
1057 command in @file{.wgetrc}. That setting may be overridden from the
1060 @cindex local encoding
1061 @item --local-encoding=@var{encoding}
1063 Force Wget to use @var{encoding} as the default system encoding. That affects
1064 how Wget converts URLs specified as arguments from locale to @sc{utf-8} for
1067 Wget use the function @code{nl_langinfo()} and then the @code{CHARSET}
1068 environment variable to get the locale. If it fails, @sc{ascii} is used.
1070 You can set the default local encoding using the @code{local_encoding}
1071 command in @file{.wgetrc}. That setting may be overridden from the
1074 @cindex remote encoding
1075 @item --remote-encoding=@var{encoding}
1077 Force Wget to use @var{encoding} as the default remote server encoding.
1078 That affects how Wget converts URIs found in files from remote encoding
1079 to @sc{utf-8} during a recursive fetch. This options is only useful for
1080 IRI support, for the interpretation of non-@sc{ascii} characters.
1082 For HTTP, remote encoding can be found in HTTP @code{Content-Type}
1083 header and in HTML @code{Content-Type http-equiv} meta tag.
1085 You can set the default encoding using the @code{remoteencoding}
1086 command in @file{.wgetrc}. That setting may be overridden from the
1092 Force Wget to unlink file instead of clobbering existing file. This
1093 option is useful for downloading to the directory with hardlinks.
1097 @node Directory Options, HTTP Options, Download Options, Invoking
1098 @section Directory Options
1102 @itemx --no-directories
1103 Do not create a hierarchy of directories when retrieving recursively.
1104 With this option turned on, all files will get saved to the current
1105 directory, without clobbering (if a name shows up more than once, the
1106 filenames will get extensions @samp{.n}).
1109 @itemx --force-directories
1110 The opposite of @samp{-nd}---create a hierarchy of directories, even if
1111 one would not have been created otherwise. E.g. @samp{wget -x
1112 http://fly.srk.fer.hr/robots.txt} will save the downloaded file to
1113 @file{fly.srk.fer.hr/robots.txt}.
1116 @itemx --no-host-directories
1117 Disable generation of host-prefixed directories. By default, invoking
1118 Wget with @samp{-r http://fly.srk.fer.hr/} will create a structure of
1119 directories beginning with @file{fly.srk.fer.hr/}. This option disables
1122 @item --protocol-directories
1123 Use the protocol name as a directory component of local file names. For
1124 example, with this option, @samp{wget -r http://@var{host}} will save to
1125 @samp{http/@var{host}/...} rather than just to @samp{@var{host}/...}.
1127 @cindex cut directories
1128 @item --cut-dirs=@var{number}
1129 Ignore @var{number} directory components. This is useful for getting a
1130 fine-grained control over the directory where recursive retrieval will
1133 Take, for example, the directory at
1134 @samp{ftp://ftp.xemacs.org/pub/xemacs/}. If you retrieve it with
1135 @samp{-r}, it will be saved locally under
1136 @file{ftp.xemacs.org/pub/xemacs/}. While the @samp{-nH} option can
1137 remove the @file{ftp.xemacs.org/} part, you are still stuck with
1138 @file{pub/xemacs}. This is where @samp{--cut-dirs} comes in handy; it
1139 makes Wget not ``see'' @var{number} remote directory components. Here
1140 are several examples of how @samp{--cut-dirs} option works.
1144 No options -> ftp.xemacs.org/pub/xemacs/
1146 -nH --cut-dirs=1 -> xemacs/
1147 -nH --cut-dirs=2 -> .
1149 --cut-dirs=1 -> ftp.xemacs.org/xemacs/
1154 If you just want to get rid of the directory structure, this option is
1155 similar to a combination of @samp{-nd} and @samp{-P}. However, unlike
1156 @samp{-nd}, @samp{--cut-dirs} does not lose with subdirectories---for
1157 instance, with @samp{-nH --cut-dirs=1}, a @file{beta/} subdirectory will
1158 be placed to @file{xemacs/beta}, as one would expect.
1160 @cindex directory prefix
1161 @item -P @var{prefix}
1162 @itemx --directory-prefix=@var{prefix}
1163 Set directory prefix to @var{prefix}. The @dfn{directory prefix} is the
1164 directory where all other files and subdirectories will be saved to,
1165 i.e. the top of the retrieval tree. The default is @samp{.} (the
1169 @node HTTP Options, HTTPS (SSL/TLS) Options, Directory Options, Invoking
1170 @section HTTP Options
1173 @cindex default page name
1175 @item --default-page=@var{name}
1176 Use @var{name} as the default file name when it isn't known (i.e., for
1177 URLs that end in a slash), instead of @file{index.html}.
1179 @cindex .html extension
1180 @cindex .css extension
1182 @itemx --adjust-extension
1183 If a file of type @samp{application/xhtml+xml} or @samp{text/html} is
1184 downloaded and the URL does not end with the regexp
1185 @samp{\.[Hh][Tt][Mm][Ll]?}, this option will cause the suffix @samp{.html}
1186 to be appended to the local filename. This is useful, for instance, when
1187 you're mirroring a remote site that uses @samp{.asp} pages, but you want
1188 the mirrored pages to be viewable on your stock Apache server. Another
1189 good use for this is when you're downloading CGI-generated materials. A URL
1190 like @samp{http://site.com/article.cgi?25} will be saved as
1191 @file{article.cgi?25.html}.
1193 Note that filenames changed in this way will be re-downloaded every time
1194 you re-mirror a site, because Wget can't tell that the local
1195 @file{@var{X}.html} file corresponds to remote URL @samp{@var{X}} (since
1196 it doesn't yet know that the URL produces output of type
1197 @samp{text/html} or @samp{application/xhtml+xml}.
1199 As of version 1.12, Wget will also ensure that any downloaded files of
1200 type @samp{text/css} end in the suffix @samp{.css}, and the option was
1201 renamed from @samp{--html-extension}, to better reflect its new
1202 behavior. The old option name is still acceptable, but should now be
1203 considered deprecated.
1205 At some point in the future, this option may well be expanded to
1206 include suffixes for other types of content, including content types
1207 that are not parsed by Wget.
1210 @cindex http password
1211 @cindex authentication
1212 @item --http-user=@var{user}
1213 @itemx --http-password=@var{password}
1214 Specify the username @var{user} and password @var{password} on an
1215 @sc{http} server. According to the type of the challenge, Wget will
1216 encode them using either the @code{basic} (insecure),
1217 the @code{digest}, or the Windows @code{NTLM} authentication scheme.
1219 Another way to specify username and password is in the @sc{url} itself
1220 (@pxref{URL Format}). Either method reveals your password to anyone who
1221 bothers to run @code{ps}. To prevent the passwords from being seen,
1222 store them in @file{.wgetrc} or @file{.netrc}, and make sure to protect
1223 those files from other users with @code{chmod}. If the passwords are
1224 really important, do not leave them lying in those files either---edit
1225 the files and delete them after Wget has started the download.
1228 For more information about security issues with Wget, @xref{Security
1232 @cindex Keep-Alive, turning off
1233 @cindex Persistent Connections, disabling
1234 @item --no-http-keep-alive
1235 Turn off the ``keep-alive'' feature for HTTP downloads. Normally, Wget
1236 asks the server to keep the connection open so that, when you download
1237 more than one document from the same server, they get transferred over
1238 the same TCP connection. This saves time and at the same time reduces
1239 the load on the server.
1241 This option is useful when, for some reason, persistent (keep-alive)
1242 connections don't work for you, for example due to a server bug or due
1243 to the inability of server-side scripts to cope with the connections.
1248 Disable server-side cache. In this case, Wget will send the remote
1249 server an appropriate directive (@samp{Pragma: no-cache}) to get the
1250 file from the remote service, rather than returning the cached version.
1251 This is especially useful for retrieving and flushing out-of-date
1252 documents on proxy servers.
1254 Caching is allowed by default.
1258 Disable the use of cookies. Cookies are a mechanism for maintaining
1259 server-side state. The server sends the client a cookie using the
1260 @code{Set-Cookie} header, and the client responds with the same cookie
1261 upon further requests. Since cookies allow the server owners to keep
1262 track of visitors and for sites to exchange this information, some
1263 consider them a breach of privacy. The default is to use cookies;
1264 however, @emph{storing} cookies is not on by default.
1266 @cindex loading cookies
1267 @cindex cookies, loading
1268 @item --load-cookies @var{file}
1269 Load cookies from @var{file} before the first HTTP retrieval.
1270 @var{file} is a textual file in the format originally used by Netscape's
1271 @file{cookies.txt} file.
1273 You will typically use this option when mirroring sites that require
1274 that you be logged in to access some or all of their content. The login
1275 process typically works by the web server issuing an @sc{http} cookie
1276 upon receiving and verifying your credentials. The cookie is then
1277 resent by the browser when accessing that part of the site, and so
1278 proves your identity.
1280 Mirroring such a site requires Wget to send the same cookies your
1281 browser sends when communicating with the site. This is achieved by
1282 @samp{--load-cookies}---simply point Wget to the location of the
1283 @file{cookies.txt} file, and it will send the same cookies your browser
1284 would send in the same situation. Different browsers keep textual
1285 cookie files in different locations:
1289 The cookies are in @file{~/.netscape/cookies.txt}.
1291 @item Mozilla and Netscape 6.x.
1292 Mozilla's cookie file is also named @file{cookies.txt}, located
1293 somewhere under @file{~/.mozilla}, in the directory of your profile.
1294 The full path usually ends up looking somewhat like
1295 @file{~/.mozilla/default/@var{some-weird-string}/cookies.txt}.
1297 @item Internet Explorer.
1298 You can produce a cookie file Wget can use by using the File menu,
1299 Import and Export, Export Cookies. This has been tested with Internet
1300 Explorer 5; it is not guaranteed to work with earlier versions.
1302 @item Other browsers.
1303 If you are using a different browser to create your cookies,
1304 @samp{--load-cookies} will only work if you can locate or produce a
1305 cookie file in the Netscape format that Wget expects.
1308 If you cannot use @samp{--load-cookies}, there might still be an
1309 alternative. If your browser supports a ``cookie manager'', you can use
1310 it to view the cookies used when accessing the site you're mirroring.
1311 Write down the name and value of the cookie, and manually instruct Wget
1312 to send those cookies, bypassing the ``official'' cookie support:
1315 wget --no-cookies --header "Cookie: @var{name}=@var{value}"
1318 @cindex saving cookies
1319 @cindex cookies, saving
1320 @item --save-cookies @var{file}
1321 Save cookies to @var{file} before exiting. This will not save cookies
1322 that have expired or that have no expiry time (so-called ``session
1323 cookies''), but also see @samp{--keep-session-cookies}.
1325 @cindex cookies, session
1326 @cindex session cookies
1327 @item --keep-session-cookies
1328 When specified, causes @samp{--save-cookies} to also save session
1329 cookies. Session cookies are normally not saved because they are
1330 meant to be kept in memory and forgotten when you exit the browser.
1331 Saving them is useful on sites that require you to log in or to visit
1332 the home page before you can access some pages. With this option,
1333 multiple Wget runs are considered a single browser session as far as
1334 the site is concerned.
1336 Since the cookie file format does not normally carry session cookies,
1337 Wget marks them with an expiry timestamp of 0. Wget's
1338 @samp{--load-cookies} recognizes those as session cookies, but it might
1339 confuse other browsers. Also note that cookies so loaded will be
1340 treated as other session cookies, which means that if you want
1341 @samp{--save-cookies} to preserve them again, you must use
1342 @samp{--keep-session-cookies} again.
1344 @cindex Content-Length, ignore
1345 @cindex ignore length
1346 @item --ignore-length
1347 Unfortunately, some @sc{http} servers (@sc{cgi} programs, to be more
1348 precise) send out bogus @code{Content-Length} headers, which makes Wget
1349 go wild, as it thinks not all the document was retrieved. You can spot
1350 this syndrome if Wget retries getting the same document again and again,
1351 each time claiming that the (otherwise normal) connection has closed on
1354 With this option, Wget will ignore the @code{Content-Length} header---as
1355 if it never existed.
1358 @item --header=@var{header-line}
1359 Send @var{header-line} along with the rest of the headers in each
1360 @sc{http} request. The supplied header is sent as-is, which means it
1361 must contain name and value separated by colon, and must not contain
1364 You may define more than one additional header by specifying
1365 @samp{--header} more than once.
1369 wget --header='Accept-Charset: iso-8859-2' \
1370 --header='Accept-Language: hr' \
1371 http://fly.srk.fer.hr/
1375 Specification of an empty string as the header value will clear all
1376 previous user-defined headers.
1378 As of Wget 1.10, this option can be used to override headers otherwise
1379 generated automatically. This example instructs Wget to connect to
1380 localhost, but to specify @samp{foo.bar} in the @code{Host} header:
1383 wget --header="Host: foo.bar" http://localhost/
1386 In versions of Wget prior to 1.10 such use of @samp{--header} caused
1387 sending of duplicate headers.
1390 @item --max-redirect=@var{number}
1391 Specifies the maximum number of redirections to follow for a resource.
1392 The default is 20, which is usually far more than necessary. However, on
1393 those occasions where you want to allow more (or fewer), this is the
1397 @cindex proxy password
1398 @cindex proxy authentication
1399 @item --proxy-user=@var{user}
1400 @itemx --proxy-password=@var{password}
1401 Specify the username @var{user} and password @var{password} for
1402 authentication on a proxy server. Wget will encode them using the
1403 @code{basic} authentication scheme.
1405 Security considerations similar to those with @samp{--http-password}
1406 pertain here as well.
1408 @cindex http referer
1409 @cindex referer, http
1410 @item --referer=@var{url}
1411 Include `Referer: @var{url}' header in HTTP request. Useful for
1412 retrieving documents with server-side processing that assume they are
1413 always being retrieved by interactive web browsers and only come out
1414 properly when Referer is set to one of the pages that point to them.
1416 @cindex server response, save
1417 @item --save-headers
1418 Save the headers sent by the @sc{http} server to the file, preceding the
1419 actual contents, with an empty line as the separator.
1422 @item -U @var{agent-string}
1423 @itemx --user-agent=@var{agent-string}
1424 Identify as @var{agent-string} to the @sc{http} server.
1426 The @sc{http} protocol allows the clients to identify themselves using a
1427 @code{User-Agent} header field. This enables distinguishing the
1428 @sc{www} software, usually for statistical purposes or for tracing of
1429 protocol violations. Wget normally identifies as
1430 @samp{Wget/@var{version}}, @var{version} being the current version
1433 However, some sites have been known to impose the policy of tailoring
1434 the output according to the @code{User-Agent}-supplied information.
1435 While this is not such a bad idea in theory, it has been abused by
1436 servers denying information to clients other than (historically)
1437 Netscape or, more frequently, Microsoft Internet Explorer. This
1438 option allows you to change the @code{User-Agent} line issued by Wget.
1439 Use of this option is discouraged, unless you really know what you are
1442 Specifying empty user agent with @samp{--user-agent=""} instructs Wget
1443 not to send the @code{User-Agent} header in @sc{http} requests.
1446 @item --post-data=@var{string}
1447 @itemx --post-file=@var{file}
1448 Use POST as the method for all HTTP requests and send the specified
1449 data in the request body. @samp{--post-data} sends @var{string} as
1450 data, whereas @samp{--post-file} sends the contents of @var{file}.
1451 Other than that, they work in exactly the same way. In particular,
1452 they @emph{both} expect content of the form @code{key1=value1&key2=value2},
1453 with percent-encoding for special characters; the only difference is
1454 that one expects its content as a command-line parameter and the other
1455 accepts its content from a file. In particular, @samp{--post-file} is
1456 @emph{not} for transmitting files as form attachments: those must
1457 appear as @code{key=value} data (with appropriate percent-coding) just
1458 like everything else. Wget does not currently support
1459 @code{multipart/form-data} for transmitting POST data; only
1460 @code{application/x-www-form-urlencoded}. Only one of
1461 @samp{--post-data} and @samp{--post-file} should be specified.
1463 Please note that wget does not require the content to be of the form
1464 @code{key1=value1&key2=value2}, and neither does it test for it. Wget will
1465 simply transmit whatever data is provided to it. Most servers however expect
1466 the POST data to be in the above format when processing HTML Forms.
1468 Please be aware that Wget needs to know the size of the POST data in
1469 advance. Therefore the argument to @code{--post-file} must be a regular
1470 file; specifying a FIFO or something like @file{/dev/stdin} won't work.
1471 It's not quite clear how to work around this limitation inherent in
1472 HTTP/1.0. Although HTTP/1.1 introduces @dfn{chunked} transfer that
1473 doesn't require knowing the request length in advance, a client can't
1474 use chunked unless it knows it's talking to an HTTP/1.1 server. And it
1475 can't know that until it receives a response, which in turn requires the
1476 request to have been completed -- a chicken-and-egg problem.
1478 Note: if Wget is redirected after the POST request is completed, it
1479 will not send the POST data to the redirected URL. This is because
1480 URLs that process POST often respond with a redirection to a regular
1481 page, which does not desire or accept POST. It is not completely
1482 clear that this behavior is optimal; if it doesn't work out, it might
1483 be changed in the future.
1485 This example shows how to log to a server using POST and then proceed to
1486 download the desired pages, presumably only accessible to authorized
1491 # @r{Log in to the server. This can be done only once.}
1492 wget --save-cookies cookies.txt \
1493 --post-data 'user=foo&password=bar' \
1494 http://server.com/auth.php
1496 # @r{Now grab the page or pages we care about.}
1497 wget --load-cookies cookies.txt \
1498 -p http://server.com/interesting/article.php
1502 If the server is using session cookies to track user authentication,
1503 the above will not work because @samp{--save-cookies} will not save
1504 them (and neither will browsers) and the @file{cookies.txt} file will
1505 be empty. In that case use @samp{--keep-session-cookies} along with
1506 @samp{--save-cookies} to force saving of session cookies.
1508 @cindex Other HTTP Methods
1509 @item --method=@var{HTTP-Method}
1510 For the purpose of RESTful scripting, Wget allows sending of other HTTP Methods
1511 without the need to explicitly set them using @samp{--header=Header-Line}.
1512 Wget will use whatever string is passed to it after @samp{--method} as the HTTP
1513 Method to the server.
1515 @item --body-data=@var{Data-String}
1516 @itemx --body-file=@var{Data-File}
1517 Must be set when additional data needs to be sent to the server along with the
1518 Method specified using @samp{--method}. @samp{--post-data} sends @var{string} as
1519 data, whereas @samp{--post-file} sends the contents of @var{file}. Other than that,
1520 they work in exactly the same way.
1522 Currently, @samp{--body-file} is @emph{not} for transmitting files as a whole.
1523 Wget does not currently support @code{multipart/form-data} for transmitting data;
1524 only @code{application/x-www-form-urlencoded}. In the future, this may be changed
1525 so that wget sends the @samp{--body-file} as a complete file instead of sending its
1526 contents to the server. Please be aware that Wget needs to know the contents of
1527 BODY Data in advance, and hence the argument to @samp{--body-file} should be a
1528 regular file. See @samp{--post-file} for a more detailed explanation.
1529 Only one of @samp{--body-data} and @samp{--body-file} should be specified.
1531 Wget handles these requests in the same way that it handles @samp{--post-data}
1532 and @samp{--post-file}. If you invoke Wget with @samp{--method=POST} and the server
1533 responds with a redirect request, then Wget will revert to a GET request during the
1534 redirection as is explained in @samp{--post-data}.
1536 @cindex Content-Disposition
1537 @item --content-disposition
1539 If this is set to on, experimental (not fully-functional) support for
1540 @code{Content-Disposition} headers is enabled. This can currently result in
1541 extra round-trips to the server for a @code{HEAD} request, and is known
1542 to suffer from a few bugs, which is why it is not currently enabled by default.
1544 This option is useful for some file-downloading CGI programs that use
1545 @code{Content-Disposition} headers to describe what the name of a
1546 downloaded file should be.
1548 @cindex Content On Error
1549 @item --content-on-error
1551 If this is set to on, wget will not skip the content when the server responds
1552 with a http status code that indicates error.
1554 @cindex Trust server names
1555 @item --trust-server-names
1557 If this is set to on, on a redirect the last component of the
1558 redirection URL will be used as the local file name. By default it is
1559 used the last component in the original URL.
1561 @cindex authentication
1562 @item --auth-no-challenge
1564 If this option is given, Wget will send Basic HTTP authentication
1565 information (plaintext username and password) for all requests, just
1566 like Wget 1.10.2 and prior did by default.
1568 Use of this option is not recommended, and is intended only to support
1569 some few obscure servers, which never send HTTP authentication
1570 challenges, but accept unsolicited auth info, say, in addition to
1571 form-based authentication.
1575 @node HTTPS (SSL/TLS) Options, FTP Options, HTTP Options, Invoking
1576 @section HTTPS (SSL/TLS) Options
1579 To support encrypted HTTP (HTTPS) downloads, Wget must be compiled
1580 with an external SSL library, currently OpenSSL. If Wget is compiled
1581 without SSL support, none of these options are available.
1584 @cindex SSL protocol, choose
1585 @item --secure-protocol=@var{protocol}
1586 Choose the secure protocol to be used. Legal values are @samp{auto},
1587 @samp{SSLv2}, @samp{SSLv3}, and @samp{TLSv1}. If @samp{auto} is used,
1588 the SSL library is given the liberty of choosing the appropriate
1589 protocol automatically, which is achieved by sending an SSLv2 greeting
1590 and announcing support for SSLv3 and TLSv1. This is the default.
1592 Specifying @samp{SSLv2}, @samp{SSLv3}, or @samp{TLSv1} forces the use
1593 of the corresponding protocol. This is useful when talking to old and
1594 buggy SSL server implementations that make it hard for OpenSSL to
1595 choose the correct protocol version. Fortunately, such servers are
1598 @cindex SSL certificate, check
1599 @item --no-check-certificate
1600 Don't check the server certificate against the available certificate
1601 authorities. Also don't require the URL host name to match the common
1602 name presented by the certificate.
1604 As of Wget 1.10, the default is to verify the server's certificate
1605 against the recognized certificate authorities, breaking the SSL
1606 handshake and aborting the download if the verification fails.
1607 Although this provides more secure downloads, it does break
1608 interoperability with some sites that worked with previous Wget
1609 versions, particularly those using self-signed, expired, or otherwise
1610 invalid certificates. This option forces an ``insecure'' mode of
1611 operation that turns the certificate verification errors into warnings
1612 and allows you to proceed.
1614 If you encounter ``certificate verification'' errors or ones saying
1615 that ``common name doesn't match requested host name'', you can use
1616 this option to bypass the verification and proceed with the download.
1617 @emph{Only use this option if you are otherwise convinced of the
1618 site's authenticity, or if you really don't care about the validity of
1619 its certificate.} It is almost always a bad idea not to check the
1620 certificates when transmitting confidential or important data.
1622 @cindex SSL certificate
1623 @item --certificate=@var{file}
1624 Use the client certificate stored in @var{file}. This is needed for
1625 servers that are configured to require certificates from the clients
1626 that connect to them. Normally a certificate is not required and this
1629 @cindex SSL certificate type, specify
1630 @item --certificate-type=@var{type}
1631 Specify the type of the client certificate. Legal values are
1632 @samp{PEM} (assumed by default) and @samp{DER}, also known as
1635 @item --private-key=@var{file}
1636 Read the private key from @var{file}. This allows you to provide the
1637 private key in a file separate from the certificate.
1639 @item --private-key-type=@var{type}
1640 Specify the type of the private key. Accepted values are @samp{PEM}
1641 (the default) and @samp{DER}.
1643 @item --ca-certificate=@var{file}
1644 Use @var{file} as the file with the bundle of certificate authorities
1645 (``CA'') to verify the peers. The certificates must be in PEM format.
1647 Without this option Wget looks for CA certificates at the
1648 system-specified locations, chosen at OpenSSL installation time.
1650 @cindex SSL certificate authority
1651 @item --ca-directory=@var{directory}
1652 Specifies directory containing CA certificates in PEM format. Each
1653 file contains one CA certificate, and the file name is based on a hash
1654 value derived from the certificate. This is achieved by processing a
1655 certificate directory with the @code{c_rehash} utility supplied with
1656 OpenSSL. Using @samp{--ca-directory} is more efficient than
1657 @samp{--ca-certificate} when many certificates are installed because
1658 it allows Wget to fetch certificates on demand.
1660 Without this option Wget looks for CA certificates at the
1661 system-specified locations, chosen at OpenSSL installation time.
1663 @cindex entropy, specifying source of
1664 @cindex randomness, specifying source of
1665 @item --random-file=@var{file}
1666 Use @var{file} as the source of random data for seeding the
1667 pseudo-random number generator on systems without @file{/dev/random}.
1669 On such systems the SSL library needs an external source of randomness
1670 to initialize. Randomness may be provided by EGD (see
1671 @samp{--egd-file} below) or read from an external source specified by
1672 the user. If this option is not specified, Wget looks for random data
1673 in @code{$RANDFILE} or, if that is unset, in @file{$HOME/.rnd}. If
1674 none of those are available, it is likely that SSL encryption will not
1677 If you're getting the ``Could not seed OpenSSL PRNG; disabling SSL.''
1678 error, you should provide random data using some of the methods
1682 @item --egd-file=@var{file}
1683 Use @var{file} as the EGD socket. EGD stands for @dfn{Entropy
1684 Gathering Daemon}, a user-space program that collects data from
1685 various unpredictable system sources and makes it available to other
1686 programs that might need it. Encryption software, such as the SSL
1687 library, needs sources of non-repeating randomness to seed the random
1688 number generator used to produce cryptographically strong keys.
1690 OpenSSL allows the user to specify his own source of entropy using the
1691 @code{RAND_FILE} environment variable. If this variable is unset, or
1692 if the specified file does not produce enough randomness, OpenSSL will
1693 read random data from EGD socket specified using this option.
1695 If this option is not specified (and the equivalent startup command is
1696 not used), EGD is never contacted. EGD is not needed on modern Unix
1697 systems that support @file{/dev/random}.
1702 @item --warc-file=@var{file}
1703 Use @var{file} as the destination WARC file.
1705 @item --warc-header=@var{string}
1706 Use @var{string} into as the warcinfo record.
1708 @item --warc-max-size=@var{size}
1709 Set the maximum size of the WARC files to @var{size}.
1712 Write CDX index files.
1714 @item --warc-dedup=@var{file}
1715 Do not store records listed in this CDX file.
1717 @item --no-warc-compression
1718 Do not compress WARC files with GZIP.
1720 @item --no-warc-digests
1721 Do not calculate SHA1 digests.
1723 @item --no-warc-keep-log
1724 Do not store the log file in a WARC record.
1726 @item --warc-tempdir=@var{dir}
1727 Specify the location for temporary files created by the WARC writer.
1730 @node FTP Options, Recursive Retrieval Options, HTTPS (SSL/TLS) Options, Invoking
1731 @section FTP Options
1735 @cindex ftp password
1736 @cindex ftp authentication
1737 @item --ftp-user=@var{user}
1738 @itemx --ftp-password=@var{password}
1739 Specify the username @var{user} and password @var{password} on an
1740 @sc{ftp} server. Without this, or the corresponding startup option,
1741 the password defaults to @samp{-wget@@}, normally used for anonymous
1744 Another way to specify username and password is in the @sc{url} itself
1745 (@pxref{URL Format}). Either method reveals your password to anyone who
1746 bothers to run @code{ps}. To prevent the passwords from being seen,
1747 store them in @file{.wgetrc} or @file{.netrc}, and make sure to protect
1748 those files from other users with @code{chmod}. If the passwords are
1749 really important, do not leave them lying in those files either---edit
1750 the files and delete them after Wget has started the download.
1753 For more information about security issues with Wget, @xref{Security
1757 @cindex .listing files, removing
1758 @item --no-remove-listing
1759 Don't remove the temporary @file{.listing} files generated by @sc{ftp}
1760 retrievals. Normally, these files contain the raw directory listings
1761 received from @sc{ftp} servers. Not removing them can be useful for
1762 debugging purposes, or when you want to be able to easily check on the
1763 contents of remote server directories (e.g. to verify that a mirror
1764 you're running is complete).
1766 Note that even though Wget writes to a known filename for this file,
1767 this is not a security hole in the scenario of a user making
1768 @file{.listing} a symbolic link to @file{/etc/passwd} or something and
1769 asking @code{root} to run Wget in his or her directory. Depending on
1770 the options used, either Wget will refuse to write to @file{.listing},
1771 making the globbing/recursion/time-stamping operation fail, or the
1772 symbolic link will be deleted and replaced with the actual
1773 @file{.listing} file, or the listing will be written to a
1774 @file{.listing.@var{number}} file.
1776 Even though this situation isn't a problem, though, @code{root} should
1777 never run Wget in a non-trusted user's directory. A user could do
1778 something as simple as linking @file{index.html} to @file{/etc/passwd}
1779 and asking @code{root} to run Wget with @samp{-N} or @samp{-r} so the file
1780 will be overwritten.
1782 @cindex globbing, toggle
1784 Turn off @sc{ftp} globbing. Globbing refers to the use of shell-like
1785 special characters (@dfn{wildcards}), like @samp{*}, @samp{?}, @samp{[}
1786 and @samp{]} to retrieve more than one file from the same directory at
1790 wget ftp://gnjilux.srk.fer.hr/*.msg
1793 By default, globbing will be turned on if the @sc{url} contains a
1794 globbing character. This option may be used to turn globbing on or off
1797 You may have to quote the @sc{url} to protect it from being expanded by
1798 your shell. Globbing makes Wget look for a directory listing, which is
1799 system-specific. This is why it currently works only with Unix @sc{ftp}
1800 servers (and the ones emulating Unix @code{ls} output).
1803 @item --no-passive-ftp
1804 Disable the use of the @dfn{passive} FTP transfer mode. Passive FTP
1805 mandates that the client connect to the server to establish the data
1806 connection rather than the other way around.
1808 If the machine is connected to the Internet directly, both passive and
1809 active FTP should work equally well. Behind most firewall and NAT
1810 configurations passive FTP has a better chance of working. However,
1811 in some rare firewall configurations, active FTP actually works when
1812 passive FTP doesn't. If you suspect this to be the case, use this
1813 option, or set @code{passive_ftp=off} in your init file.
1815 @cindex symbolic links, retrieving
1816 @item --retr-symlinks
1817 Usually, when retrieving @sc{ftp} directories recursively and a symbolic
1818 link is encountered, the linked-to file is not downloaded. Instead, a
1819 matching symbolic link is created on the local filesystem. The
1820 pointed-to file will not be downloaded unless this recursive retrieval
1821 would have encountered it separately and downloaded it anyway.
1823 When @samp{--retr-symlinks} is specified, however, symbolic links are
1824 traversed and the pointed-to files are retrieved. At this time, this
1825 option does not cause Wget to traverse symlinks to directories and
1826 recurse through them, but in the future it should be enhanced to do
1829 Note that when retrieving a file (not a directory) because it was
1830 specified on the command-line, rather than because it was recursed to,
1831 this option has no effect. Symbolic links are always traversed in this
1835 @node Recursive Retrieval Options, Recursive Accept/Reject Options, FTP Options, Invoking
1836 @section Recursive Retrieval Options
1841 Turn on recursive retrieving. @xref{Recursive Download}, for more
1842 details. The default maximum depth is 5.
1844 @item -l @var{depth}
1845 @itemx --level=@var{depth}
1846 Specify recursion maximum depth level @var{depth} (@pxref{Recursive
1849 @cindex proxy filling
1850 @cindex delete after retrieval
1851 @cindex filling proxy cache
1852 @item --delete-after
1853 This option tells Wget to delete every single file it downloads,
1854 @emph{after} having done so. It is useful for pre-fetching popular
1855 pages through a proxy, e.g.:
1858 wget -r -nd --delete-after http://whatever.com/~popular/page/
1861 The @samp{-r} option is to retrieve recursively, and @samp{-nd} to not
1864 Note that @samp{--delete-after} deletes files on the local machine. It
1865 does not issue the @samp{DELE} command to remote FTP sites, for
1866 instance. Also note that when @samp{--delete-after} is specified,
1867 @samp{--convert-links} is ignored, so @samp{.orig} files are simply not
1868 created in the first place.
1870 @cindex conversion of links
1871 @cindex link conversion
1873 @itemx --convert-links
1874 After the download is complete, convert the links in the document to
1875 make them suitable for local viewing. This affects not only the visible
1876 hyperlinks, but any part of the document that links to external content,
1877 such as embedded images, links to style sheets, hyperlinks to non-@sc{html}
1880 Each link will be changed in one of the two ways:
1884 The links to files that have been downloaded by Wget will be changed to
1885 refer to the file they point to as a relative link.
1887 Example: if the downloaded file @file{/foo/doc.html} links to
1888 @file{/bar/img.gif}, also downloaded, then the link in @file{doc.html}
1889 will be modified to point to @samp{../bar/img.gif}. This kind of
1890 transformation works reliably for arbitrary combinations of directories.
1893 The links to files that have not been downloaded by Wget will be changed
1894 to include host name and absolute path of the location they point to.
1896 Example: if the downloaded file @file{/foo/doc.html} links to
1897 @file{/bar/img.gif} (or to @file{../bar/img.gif}), then the link in
1898 @file{doc.html} will be modified to point to
1899 @file{http://@var{hostname}/bar/img.gif}.
1902 Because of this, local browsing works reliably: if a linked file was
1903 downloaded, the link will refer to its local name; if it was not
1904 downloaded, the link will refer to its full Internet address rather than
1905 presenting a broken link. The fact that the former links are converted
1906 to relative links ensures that you can move the downloaded hierarchy to
1909 Note that only at the end of the download can Wget know which links have
1910 been downloaded. Because of that, the work done by @samp{-k} will be
1911 performed at the end of all the downloads.
1913 @cindex backing up converted files
1915 @itemx --backup-converted
1916 When converting a file, back up the original version with a @samp{.orig}
1917 suffix. Affects the behavior of @samp{-N} (@pxref{HTTP Time-Stamping
1922 Turn on options suitable for mirroring. This option turns on recursion
1923 and time-stamping, sets infinite recursion depth and keeps @sc{ftp}
1924 directory listings. It is currently equivalent to
1925 @samp{-r -N -l inf --no-remove-listing}.
1927 @cindex page requisites
1928 @cindex required images, downloading
1930 @itemx --page-requisites
1931 This option causes Wget to download all the files that are necessary to
1932 properly display a given @sc{html} page. This includes such things as
1933 inlined images, sounds, and referenced stylesheets.
1935 Ordinarily, when downloading a single @sc{html} page, any requisite documents
1936 that may be needed to display it properly are not downloaded. Using
1937 @samp{-r} together with @samp{-l} can help, but since Wget does not
1938 ordinarily distinguish between external and inlined documents, one is
1939 generally left with ``leaf documents'' that are missing their
1942 For instance, say document @file{1.html} contains an @code{<IMG>} tag
1943 referencing @file{1.gif} and an @code{<A>} tag pointing to external
1944 document @file{2.html}. Say that @file{2.html} is similar but that its
1945 image is @file{2.gif} and it links to @file{3.html}. Say this
1946 continues up to some arbitrarily high number.
1948 If one executes the command:
1951 wget -r -l 2 http://@var{site}/1.html
1954 then @file{1.html}, @file{1.gif}, @file{2.html}, @file{2.gif}, and
1955 @file{3.html} will be downloaded. As you can see, @file{3.html} is
1956 without its requisite @file{3.gif} because Wget is simply counting the
1957 number of hops (up to 2) away from @file{1.html} in order to determine
1958 where to stop the recursion. However, with this command:
1961 wget -r -l 2 -p http://@var{site}/1.html
1964 all the above files @emph{and} @file{3.html}'s requisite @file{3.gif}
1965 will be downloaded. Similarly,
1968 wget -r -l 1 -p http://@var{site}/1.html
1971 will cause @file{1.html}, @file{1.gif}, @file{2.html}, and @file{2.gif}
1972 to be downloaded. One might think that:
1975 wget -r -l 0 -p http://@var{site}/1.html
1978 would download just @file{1.html} and @file{1.gif}, but unfortunately
1979 this is not the case, because @samp{-l 0} is equivalent to
1980 @samp{-l inf}---that is, infinite recursion. To download a single @sc{html}
1981 page (or a handful of them, all specified on the command-line or in a
1982 @samp{-i} @sc{url} input file) and its (or their) requisites, simply leave off
1983 @samp{-r} and @samp{-l}:
1986 wget -p http://@var{site}/1.html
1989 Note that Wget will behave as if @samp{-r} had been specified, but only
1990 that single page and its requisites will be downloaded. Links from that
1991 page to external documents will not be followed. Actually, to download
1992 a single page and all its requisites (even if they exist on separate
1993 websites), and make sure the lot displays properly locally, this author
1994 likes to use a few options in addition to @samp{-p}:
1997 wget -E -H -k -K -p http://@var{site}/@var{document}
2000 To finish off this topic, it's worth knowing that Wget's idea of an
2001 external document link is any URL specified in an @code{<A>} tag, an
2002 @code{<AREA>} tag, or a @code{<LINK>} tag other than @code{<LINK
2005 @cindex @sc{html} comments
2006 @cindex comments, @sc{html}
2007 @item --strict-comments
2008 Turn on strict parsing of @sc{html} comments. The default is to terminate
2009 comments at the first occurrence of @samp{-->}.
2011 According to specifications, @sc{html} comments are expressed as @sc{sgml}
2012 @dfn{declarations}. Declaration is special markup that begins with
2013 @samp{<!} and ends with @samp{>}, such as @samp{<!DOCTYPE ...>}, that
2014 may contain comments between a pair of @samp{--} delimiters. @sc{html}
2015 comments are ``empty declarations'', @sc{sgml} declarations without any
2016 non-comment text. Therefore, @samp{<!--foo-->} is a valid comment, and
2017 so is @samp{<!--one-- --two-->}, but @samp{<!--1--2-->} is not.
2019 On the other hand, most @sc{html} writers don't perceive comments as anything
2020 other than text delimited with @samp{<!--} and @samp{-->}, which is not
2021 quite the same. For example, something like @samp{<!------------>}
2022 works as a valid comment as long as the number of dashes is a multiple
2023 of four (!). If not, the comment technically lasts until the next
2024 @samp{--}, which may be at the other end of the document. Because of
2025 this, many popular browsers completely ignore the specification and
2026 implement what users have come to expect: comments delimited with
2027 @samp{<!--} and @samp{-->}.
2029 Until version 1.9, Wget interpreted comments strictly, which resulted in
2030 missing links in many web pages that displayed fine in browsers, but had
2031 the misfortune of containing non-compliant comments. Beginning with
2032 version 1.9, Wget has joined the ranks of clients that implements
2033 ``naive'' comments, terminating each comment at the first occurrence of
2036 If, for whatever reason, you want strict comment parsing, use this
2037 option to turn it on.
2040 @node Recursive Accept/Reject Options, Exit Status, Recursive Retrieval Options, Invoking
2041 @section Recursive Accept/Reject Options
2044 @item -A @var{acclist} --accept @var{acclist}
2045 @itemx -R @var{rejlist} --reject @var{rejlist}
2046 Specify comma-separated lists of file name suffixes or patterns to
2047 accept or reject (@pxref{Types of Files}). Note that if
2048 any of the wildcard characters, @samp{*}, @samp{?}, @samp{[} or
2049 @samp{]}, appear in an element of @var{acclist} or @var{rejlist},
2050 it will be treated as a pattern, rather than a suffix.
2052 @item -D @var{domain-list}
2053 @itemx --domains=@var{domain-list}
2054 Set domains to be followed. @var{domain-list} is a comma-separated list
2055 of domains. Note that it does @emph{not} turn on @samp{-H}.
2057 @item --exclude-domains @var{domain-list}
2058 Specify the domains that are @emph{not} to be followed
2059 (@pxref{Spanning Hosts}).
2061 @cindex follow FTP links
2063 Follow @sc{ftp} links from @sc{html} documents. Without this option,
2064 Wget will ignore all the @sc{ftp} links.
2066 @cindex tag-based recursive pruning
2067 @item --follow-tags=@var{list}
2068 Wget has an internal table of @sc{html} tag / attribute pairs that it
2069 considers when looking for linked documents during a recursive
2070 retrieval. If a user wants only a subset of those tags to be
2071 considered, however, he or she should be specify such tags in a
2072 comma-separated @var{list} with this option.
2074 @item --ignore-tags=@var{list}
2075 This is the opposite of the @samp{--follow-tags} option. To skip
2076 certain @sc{html} tags when recursively looking for documents to download,
2077 specify them in a comma-separated @var{list}.
2079 In the past, this option was the best bet for downloading a single page
2080 and its requisites, using a command-line like:
2083 wget --ignore-tags=a,area -H -k -K -r http://@var{site}/@var{document}
2086 However, the author of this option came across a page with tags like
2087 @code{<LINK REL="home" HREF="/">} and came to the realization that
2088 specifying tags to ignore was not enough. One can't just tell Wget to
2089 ignore @code{<LINK>}, because then stylesheets will not be downloaded.
2090 Now the best bet for downloading a single page and its requisites is the
2091 dedicated @samp{--page-requisites} option.
2096 Ignore case when matching files and directories. This influences the
2097 behavior of -R, -A, -I, and -X options, as well as globbing
2098 implemented when downloading from FTP sites. For example, with this
2099 option, @samp{-A *.txt} will match @samp{file1.txt}, but also
2100 @samp{file2.TXT}, @samp{file3.TxT}, and so on.
2104 Enable spanning across hosts when doing recursive retrieving
2105 (@pxref{Spanning Hosts}).
2109 Follow relative links only. Useful for retrieving a specific home page
2110 without any distractions, not even those from the same hosts
2111 (@pxref{Relative Links}).
2114 @itemx --include-directories=@var{list}
2115 Specify a comma-separated list of directories you wish to follow when
2116 downloading (@pxref{Directory-Based Limits}). Elements
2117 of @var{list} may contain wildcards.
2120 @itemx --exclude-directories=@var{list}
2121 Specify a comma-separated list of directories you wish to exclude from
2122 download (@pxref{Directory-Based Limits}). Elements of
2123 @var{list} may contain wildcards.
2127 Do not ever ascend to the parent directory when retrieving recursively.
2128 This is a useful option, since it guarantees that only the files
2129 @emph{below} a certain hierarchy will be downloaded.
2130 @xref{Directory-Based Limits}, for more details.
2135 @node Exit Status, , Recursive Accept/Reject Options, Invoking
2136 @section Exit Status
2138 @c man begin EXITSTATUS
2140 Wget may return one of several error codes if it encounters problems.
2145 No problems occurred.
2151 Parse error---for instance, when parsing command-line options, the
2152 @samp{.wgetrc} or @samp{.netrc}...
2161 SSL verification failure.
2164 Username/password authentication failure.
2170 Server issued an error response.
2174 With the exceptions of 0 and 1, the lower-numbered exit codes take
2175 precedence over higher-numbered ones, when multiple types of errors
2178 In versions of Wget prior to 1.12, Wget's exit status tended to be
2179 unhelpful and inconsistent. Recursive downloads would virtually always
2180 return 0 (success), regardless of any issues encountered, and
2181 non-recursive fetches only returned the status corresponding to the
2182 most recently-attempted download.
2186 @node Recursive Download, Following Links, Invoking, Top
2187 @chapter Recursive Download
2190 @cindex recursive download
2192 GNU Wget is capable of traversing parts of the Web (or a single
2193 @sc{http} or @sc{ftp} server), following links and directory structure.
2194 We refer to this as to @dfn{recursive retrieval}, or @dfn{recursion}.
2196 With @sc{http} @sc{url}s, Wget retrieves and parses the @sc{html} or
2197 @sc{css} from the given @sc{url}, retrieving the files the document
2198 refers to, through markup like @code{href} or @code{src}, or @sc{css}
2199 @sc{uri} values specified using the @samp{url()} functional notation.
2200 If the freshly downloaded file is also of type @code{text/html},
2201 @code{application/xhtml+xml}, or @code{text/css}, it will be parsed
2202 and followed further.
2204 Recursive retrieval of @sc{http} and @sc{html}/@sc{css} content is
2205 @dfn{breadth-first}. This means that Wget first downloads the requested
2206 document, then the documents linked from that document, then the
2207 documents linked by them, and so on. In other words, Wget first
2208 downloads the documents at depth 1, then those at depth 2, and so on
2209 until the specified maximum depth.
2211 The maximum @dfn{depth} to which the retrieval may descend is specified
2212 with the @samp{-l} option. The default maximum depth is five layers.
2214 When retrieving an @sc{ftp} @sc{url} recursively, Wget will retrieve all
2215 the data from the given directory tree (including the subdirectories up
2216 to the specified depth) on the remote server, creating its mirror image
2217 locally. @sc{ftp} retrieval is also limited by the @code{depth}
2218 parameter. Unlike @sc{http} recursion, @sc{ftp} recursion is performed
2221 By default, Wget will create a local directory tree, corresponding to
2222 the one found on the remote server.
2224 Recursive retrieving can find a number of applications, the most
2225 important of which is mirroring. It is also useful for @sc{www}
2226 presentations, and any other opportunities where slow network
2227 connections should be bypassed by storing the files locally.
2229 You should be warned that recursive downloads can overload the remote
2230 servers. Because of that, many administrators frown upon them and may
2231 ban access from your site if they detect very fast downloads of big
2232 amounts of content. When downloading from Internet servers, consider
2233 using the @samp{-w} option to introduce a delay between accesses to the
2234 server. The download will take a while longer, but the server
2235 administrator will not be alarmed by your rudeness.
2237 Of course, recursive download may cause problems on your machine. If
2238 left to run unchecked, it can easily fill up the disk. If downloading
2239 from local network, it can also take bandwidth on the system, as well as
2240 consume memory and CPU.
2242 Try to specify the criteria that match the kind of download you are
2243 trying to achieve. If you want to download only one page, use
2244 @samp{--page-requisites} without any additional recursion. If you want
2245 to download things under one directory, use @samp{-np} to avoid
2246 downloading things from other directories. If you want to download all
2247 the files from one directory, use @samp{-l 1} to make sure the recursion
2248 depth never exceeds one. @xref{Following Links}, for more information
2251 Recursive retrieval should be used with care. Don't say you were not
2254 @node Following Links, Time-Stamping, Recursive Download, Top
2255 @chapter Following Links
2257 @cindex following links
2259 When retrieving recursively, one does not wish to retrieve loads of
2260 unnecessary data. Most of the time the users bear in mind exactly what
2261 they want to download, and want Wget to follow only specific links.
2263 For example, if you wish to download the music archive from
2264 @samp{fly.srk.fer.hr}, you will not want to download all the home pages
2265 that happen to be referenced by an obscure part of the archive.
2267 Wget possesses several mechanisms that allows you to fine-tune which
2268 links it will follow.
2271 * Spanning Hosts:: (Un)limiting retrieval based on host name.
2272 * Types of Files:: Getting only certain files.
2273 * Directory-Based Limits:: Getting only certain directories.
2274 * Relative Links:: Follow relative links only.
2275 * FTP Links:: Following FTP links.
2278 @node Spanning Hosts, Types of Files, Following Links, Following Links
2279 @section Spanning Hosts
2280 @cindex spanning hosts
2281 @cindex hosts, spanning
2283 Wget's recursive retrieval normally refuses to visit hosts different
2284 than the one you specified on the command line. This is a reasonable
2285 default; without it, every retrieval would have the potential to turn
2286 your Wget into a small version of google.
2288 However, visiting different hosts, or @dfn{host spanning,} is sometimes
2289 a useful option. Maybe the images are served from a different server.
2290 Maybe you're mirroring a site that consists of pages interlinked between
2291 three servers. Maybe the server has two equivalent names, and the @sc{html}
2292 pages refer to both interchangeably.
2295 @item Span to any host---@samp{-H}
2297 The @samp{-H} option turns on host spanning, thus allowing Wget's
2298 recursive run to visit any host referenced by a link. Unless sufficient
2299 recursion-limiting criteria are applied depth, these foreign hosts will
2300 typically link to yet more hosts, and so on until Wget ends up sucking
2301 up much more data than you have intended.
2303 @item Limit spanning to certain domains---@samp{-D}
2305 The @samp{-D} option allows you to specify the domains that will be
2306 followed, thus limiting the recursion only to the hosts that belong to
2307 these domains. Obviously, this makes sense only in conjunction with
2308 @samp{-H}. A typical example would be downloading the contents of
2309 @samp{www.server.com}, but allowing downloads from
2310 @samp{images.server.com}, etc.:
2313 wget -rH -Dserver.com http://www.server.com/
2316 You can specify more than one address by separating them with a comma,
2317 e.g. @samp{-Ddomain1.com,domain2.com}.
2319 @item Keep download off certain domains---@samp{--exclude-domains}
2321 If there are domains you want to exclude specifically, you can do it
2322 with @samp{--exclude-domains}, which accepts the same type of arguments
2323 of @samp{-D}, but will @emph{exclude} all the listed domains. For
2324 example, if you want to download all the hosts from @samp{foo.edu}
2325 domain, with the exception of @samp{sunsite.foo.edu}, you can do it like
2329 wget -rH -Dfoo.edu --exclude-domains sunsite.foo.edu \
2335 @node Types of Files, Directory-Based Limits, Spanning Hosts, Following Links
2336 @section Types of Files
2337 @cindex types of files
2339 When downloading material from the web, you will often want to restrict
2340 the retrieval to only certain file types. For example, if you are
2341 interested in downloading @sc{gif}s, you will not be overjoyed to get
2342 loads of PostScript documents, and vice versa.
2344 Wget offers two options to deal with this problem. Each option
2345 description lists a short name, a long name, and the equivalent command
2348 @cindex accept wildcards
2349 @cindex accept suffixes
2350 @cindex wildcards, accept
2351 @cindex suffixes, accept
2353 @item -A @var{acclist}
2354 @itemx --accept @var{acclist}
2355 @itemx accept = @var{acclist}
2356 @itemx --accept-regex @var{urlregex}
2357 @itemx accept-regex = @var{urlregex}
2358 The argument to @samp{--accept} option is a list of file suffixes or
2359 patterns that Wget will download during recursive retrieval. A suffix
2360 is the ending part of a file, and consists of ``normal'' letters,
2361 e.g. @samp{gif} or @samp{.jpg}. A matching pattern contains shell-like
2362 wildcards, e.g. @samp{books*} or @samp{zelazny*196[0-9]*}.
2364 So, specifying @samp{wget -A gif,jpg} will make Wget download only the
2365 files ending with @samp{gif} or @samp{jpg}, i.e. @sc{gif}s and
2366 @sc{jpeg}s. On the other hand, @samp{wget -A "zelazny*196[0-9]*"} will
2367 download only files beginning with @samp{zelazny} and containing numbers
2368 from 1960 to 1969 anywhere within. Look up the manual of your shell for
2369 a description of how pattern matching works.
2371 Of course, any number of suffixes and patterns can be combined into a
2372 comma-separated list, and given as an argument to @samp{-A}.
2374 The argument to @samp{--accept-regex} option is a regular expression which
2375 is matched against the complete URL.
2377 @cindex reject wildcards
2378 @cindex reject suffixes
2379 @cindex wildcards, reject
2380 @cindex suffixes, reject
2381 @item -R @var{rejlist}
2382 @itemx --reject @var{rejlist}
2383 @itemx reject = @var{rejlist}
2384 @itemx --reject-regex @var{urlregex}
2385 @itemx reject-regex = @var{urlregex}
2386 The @samp{--reject} option works the same way as @samp{--accept}, only
2387 its logic is the reverse; Wget will download all files @emph{except} the
2388 ones matching the suffixes (or patterns) in the list.
2390 So, if you want to download a whole page except for the cumbersome
2391 @sc{mpeg}s and @sc{.au} files, you can use @samp{wget -R mpg,mpeg,au}.
2392 Analogously, to download all files except the ones beginning with
2393 @samp{bjork}, use @samp{wget -R "bjork*"}. The quotes are to prevent
2394 expansion by the shell.
2397 The argument to @samp{--accept-regex} option is a regular expression which
2398 is matched against the complete URL.
2401 The @samp{-A} and @samp{-R} options may be combined to achieve even
2402 better fine-tuning of which files to retrieve. E.g. @samp{wget -A
2403 "*zelazny*" -R .ps} will download all the files having @samp{zelazny} as
2404 a part of their name, but @emph{not} the PostScript files.
2406 Note that these two options do not affect the downloading of @sc{html}
2407 files (as determined by a @samp{.htm} or @samp{.html} filename
2408 prefix). This behavior may not be desirable for all users, and may be
2409 changed for future versions of Wget.
2411 Note, too, that query strings (strings at the end of a URL beginning
2412 with a question mark (@samp{?}) are not included as part of the
2413 filename for accept/reject rules, even though these will actually
2414 contribute to the name chosen for the local file. It is expected that
2415 a future version of Wget will provide an option to allow matching
2416 against query strings.
2418 Finally, it's worth noting that the accept/reject lists are matched
2419 @emph{twice} against downloaded files: once against the URL's filename
2420 portion, to determine if the file should be downloaded in the first
2421 place; then, after it has been accepted and successfully downloaded,
2422 the local file's name is also checked against the accept/reject lists
2423 to see if it should be removed. The rationale was that, since
2424 @samp{.htm} and @samp{.html} files are always downloaded regardless of
2425 accept/reject rules, they should be removed @emph{after} being
2426 downloaded and scanned for links, if they did match the accept/reject
2427 lists. However, this can lead to unexpected results, since the local
2428 filenames can differ from the original URL filenames in the following
2429 ways, all of which can change whether an accept/reject rule matches:
2433 If the local file already exists and @samp{--no-directories} was
2434 specified, a numeric suffix will be appended to the original name.
2436 If @samp{--adjust-extension} was specified, the local filename might have
2437 @samp{.html} appended to it. If Wget is invoked with @samp{-E -A.php},
2438 a filename such as @samp{index.php} will match be accepted, but upon
2439 download will be named @samp{index.php.html}, which no longer matches,
2440 and so the file will be deleted.
2442 Query strings do not contribute to URL matching, but are included in
2443 local filenames, and so @emph{do} contribute to filename matching.
2447 This behavior, too, is considered less-than-desirable, and may change
2448 in a future version of Wget.
2450 @node Directory-Based Limits, Relative Links, Types of Files, Following Links
2451 @section Directory-Based Limits
2453 @cindex directory limits
2455 Regardless of other link-following facilities, it is often useful to
2456 place the restriction of what files to retrieve based on the directories
2457 those files are placed in. There can be many reasons for this---the
2458 home pages may be organized in a reasonable directory structure; or some
2459 directories may contain useless information, e.g. @file{/cgi-bin} or
2460 @file{/dev} directories.
2462 Wget offers three different options to deal with this requirement. Each
2463 option description lists a short name, a long name, and the equivalent
2464 command in @file{.wgetrc}.
2466 @cindex directories, include
2467 @cindex include directories
2468 @cindex accept directories
2471 @itemx --include @var{list}
2472 @itemx include_directories = @var{list}
2473 @samp{-I} option accepts a comma-separated list of directories included
2474 in the retrieval. Any other directories will simply be ignored. The
2475 directories are absolute paths.
2477 So, if you wish to download from @samp{http://host/people/bozo/}
2478 following only links to bozo's colleagues in the @file{/people}
2479 directory and the bogus scripts in @file{/cgi-bin}, you can specify:
2482 wget -I /people,/cgi-bin http://host/people/bozo/
2485 @cindex directories, exclude
2486 @cindex exclude directories
2487 @cindex reject directories
2489 @itemx --exclude @var{list}
2490 @itemx exclude_directories = @var{list}
2491 @samp{-X} option is exactly the reverse of @samp{-I}---this is a list of
2492 directories @emph{excluded} from the download. E.g. if you do not want
2493 Wget to download things from @file{/cgi-bin} directory, specify @samp{-X
2494 /cgi-bin} on the command line.
2496 The same as with @samp{-A}/@samp{-R}, these two options can be combined
2497 to get a better fine-tuning of downloading subdirectories. E.g. if you
2498 want to load all the files from @file{/pub} hierarchy except for
2499 @file{/pub/worthless}, specify @samp{-I/pub -X/pub/worthless}.
2504 @itemx no_parent = on
2505 The simplest, and often very useful way of limiting directories is
2506 disallowing retrieval of the links that refer to the hierarchy
2507 @dfn{above} than the beginning directory, i.e. disallowing ascent to the
2508 parent directory/directories.
2510 The @samp{--no-parent} option (short @samp{-np}) is useful in this case.
2511 Using it guarantees that you will never leave the existing hierarchy.
2512 Supposing you issue Wget with:
2515 wget -r --no-parent http://somehost/~luzer/my-archive/
2518 You may rest assured that none of the references to
2519 @file{/~his-girls-homepage/} or @file{/~luzer/all-my-mpegs/} will be
2520 followed. Only the archive you are interested in will be downloaded.
2521 Essentially, @samp{--no-parent} is similar to
2522 @samp{-I/~luzer/my-archive}, only it handles redirections in a more
2523 intelligent fashion.
2525 @strong{Note} that, for HTTP (and HTTPS), the trailing slash is very
2526 important to @samp{--no-parent}. HTTP has no concept of a ``directory''---Wget
2527 relies on you to indicate what's a directory and what isn't. In
2528 @samp{http://foo/bar/}, Wget will consider @samp{bar} to be a
2529 directory, while in @samp{http://foo/bar} (no trailing slash),
2530 @samp{bar} will be considered a filename (so @samp{--no-parent} would be
2531 meaningless, as its parent is @samp{/}).
2534 @node Relative Links, FTP Links, Directory-Based Limits, Following Links
2535 @section Relative Links
2536 @cindex relative links
2538 When @samp{-L} is turned on, only the relative links are ever followed.
2539 Relative links are here defined those that do not refer to the web
2540 server root. For example, these links are relative:
2544 <a href="foo/bar.gif">
2545 <a href="../foo/bar.gif">
2548 These links are not relative:
2552 <a href="/foo/bar.gif">
2553 <a href="http://www.server.com/foo/bar.gif">
2556 Using this option guarantees that recursive retrieval will not span
2557 hosts, even without @samp{-H}. In simple cases it also allows downloads
2558 to ``just work'' without having to convert links.
2560 This option is probably not very useful and might be removed in a future
2563 @node FTP Links, , Relative Links, Following Links
2564 @section Following FTP Links
2565 @cindex following ftp links
2567 The rules for @sc{ftp} are somewhat specific, as it is necessary for
2568 them to be. @sc{ftp} links in @sc{html} documents are often included
2569 for purposes of reference, and it is often inconvenient to download them
2572 To have @sc{ftp} links followed from @sc{html} documents, you need to
2573 specify the @samp{--follow-ftp} option. Having done that, @sc{ftp}
2574 links will span hosts regardless of @samp{-H} setting. This is logical,
2575 as @sc{ftp} links rarely point to the same host where the @sc{http}
2576 server resides. For similar reasons, the @samp{-L} options has no
2577 effect on such downloads. On the other hand, domain acceptance
2578 (@samp{-D}) and suffix rules (@samp{-A} and @samp{-R}) apply normally.
2580 Also note that followed links to @sc{ftp} directories will not be
2581 retrieved recursively further.
2583 @node Time-Stamping, Startup File, Following Links, Top
2584 @chapter Time-Stamping
2585 @cindex time-stamping
2586 @cindex timestamping
2587 @cindex updating the archives
2588 @cindex incremental updating
2590 One of the most important aspects of mirroring information from the
2591 Internet is updating your archives.
2593 Downloading the whole archive again and again, just to replace a few
2594 changed files is expensive, both in terms of wasted bandwidth and money,
2595 and the time to do the update. This is why all the mirroring tools
2596 offer the option of incremental updating.
2598 Such an updating mechanism means that the remote server is scanned in
2599 search of @dfn{new} files. Only those new files will be downloaded in
2600 the place of the old ones.
2602 A file is considered new if one of these two conditions are met:
2606 A file of that name does not already exist locally.
2609 A file of that name does exist, but the remote file was modified more
2610 recently than the local file.
2613 To implement this, the program needs to be aware of the time of last
2614 modification of both local and remote files. We call this information the
2615 @dfn{time-stamp} of a file.
2617 The time-stamping in GNU Wget is turned on using @samp{--timestamping}
2618 (@samp{-N}) option, or through @code{timestamping = on} directive in
2619 @file{.wgetrc}. With this option, for each file it intends to download,
2620 Wget will check whether a local file of the same name exists. If it
2621 does, and the remote file is not newer, Wget will not download it.
2623 If the local file does not exist, or the sizes of the files do not
2624 match, Wget will download the remote file no matter what the time-stamps
2628 * Time-Stamping Usage::
2629 * HTTP Time-Stamping Internals::
2630 * FTP Time-Stamping Internals::
2633 @node Time-Stamping Usage, HTTP Time-Stamping Internals, Time-Stamping, Time-Stamping
2634 @section Time-Stamping Usage
2635 @cindex time-stamping usage
2636 @cindex usage, time-stamping
2638 The usage of time-stamping is simple. Say you would like to download a
2639 file so that it keeps its date of modification.
2642 wget -S http://www.gnu.ai.mit.edu/
2645 A simple @code{ls -l} shows that the time stamp on the local file equals
2646 the state of the @code{Last-Modified} header, as returned by the server.
2647 As you can see, the time-stamping info is preserved locally, even
2648 without @samp{-N} (at least for @sc{http}).
2650 Several days later, you would like Wget to check if the remote file has
2651 changed, and download it if it has.
2654 wget -N http://www.gnu.ai.mit.edu/
2657 Wget will ask the server for the last-modified date. If the local file
2658 has the same timestamp as the server, or a newer one, the remote file
2659 will not be re-fetched. However, if the remote file is more recent,
2660 Wget will proceed to fetch it.
2662 The same goes for @sc{ftp}. For example:
2665 wget "ftp://ftp.ifi.uio.no/pub/emacs/gnus/*"
2668 (The quotes around that URL are to prevent the shell from trying to
2669 interpret the @samp{*}.)
2671 After download, a local directory listing will show that the timestamps
2672 match those on the remote server. Reissuing the command with @samp{-N}
2673 will make Wget re-fetch @emph{only} the files that have been modified
2674 since the last download.
2676 If you wished to mirror the GNU archive every week, you would use a
2677 command like the following, weekly:
2680 wget --timestamping -r ftp://ftp.gnu.org/pub/gnu/
2683 Note that time-stamping will only work for files for which the server
2684 gives a timestamp. For @sc{http}, this depends on getting a
2685 @code{Last-Modified} header. For @sc{ftp}, this depends on getting a
2686 directory listing with dates in a format that Wget can parse
2687 (@pxref{FTP Time-Stamping Internals}).
2689 @node HTTP Time-Stamping Internals, FTP Time-Stamping Internals, Time-Stamping Usage, Time-Stamping
2690 @section HTTP Time-Stamping Internals
2691 @cindex http time-stamping
2693 Time-stamping in @sc{http} is implemented by checking of the
2694 @code{Last-Modified} header. If you wish to retrieve the file
2695 @file{foo.html} through @sc{http}, Wget will check whether
2696 @file{foo.html} exists locally. If it doesn't, @file{foo.html} will be
2697 retrieved unconditionally.
2699 If the file does exist locally, Wget will first check its local
2700 time-stamp (similar to the way @code{ls -l} checks it), and then send a
2701 @code{HEAD} request to the remote server, demanding the information on
2704 The @code{Last-Modified} header is examined to find which file was
2705 modified more recently (which makes it ``newer''). If the remote file
2706 is newer, it will be downloaded; if it is older, Wget will give
2707 up.@footnote{As an additional check, Wget will look at the
2708 @code{Content-Length} header, and compare the sizes; if they are not the
2709 same, the remote file will be downloaded no matter what the time-stamp
2712 When @samp{--backup-converted} (@samp{-K}) is specified in conjunction
2713 with @samp{-N}, server file @samp{@var{X}} is compared to local file
2714 @samp{@var{X}.orig}, if extant, rather than being compared to local file
2715 @samp{@var{X}}, which will always differ if it's been converted by
2716 @samp{--convert-links} (@samp{-k}).
2718 Arguably, @sc{http} time-stamping should be implemented using the
2719 @code{If-Modified-Since} request.
2721 @node FTP Time-Stamping Internals, , HTTP Time-Stamping Internals, Time-Stamping
2722 @section FTP Time-Stamping Internals
2723 @cindex ftp time-stamping
2725 In theory, @sc{ftp} time-stamping works much the same as @sc{http}, only
2726 @sc{ftp} has no headers---time-stamps must be ferreted out of directory
2729 If an @sc{ftp} download is recursive or uses globbing, Wget will use the
2730 @sc{ftp} @code{LIST} command to get a file listing for the directory
2731 containing the desired file(s). It will try to analyze the listing,
2732 treating it like Unix @code{ls -l} output, extracting the time-stamps.
2733 The rest is exactly the same as for @sc{http}. Note that when
2734 retrieving individual files from an @sc{ftp} server without using
2735 globbing or recursion, listing files will not be downloaded (and thus
2736 files will not be time-stamped) unless @samp{-N} is specified.
2738 Assumption that every directory listing is a Unix-style listing may
2739 sound extremely constraining, but in practice it is not, as many
2740 non-Unix @sc{ftp} servers use the Unixoid listing format because most
2741 (all?) of the clients understand it. Bear in mind that @sc{rfc959}
2742 defines no standard way to get a file list, let alone the time-stamps.
2743 We can only hope that a future standard will define this.
2745 Another non-standard solution includes the use of @code{MDTM} command
2746 that is supported by some @sc{ftp} servers (including the popular
2747 @code{wu-ftpd}), which returns the exact time of the specified file.
2748 Wget may support this command in the future.
2750 @node Startup File, Examples, Time-Stamping, Top
2751 @chapter Startup File
2752 @cindex startup file
2758 Once you know how to change default settings of Wget through command
2759 line arguments, you may wish to make some of those settings permanent.
2760 You can do that in a convenient way by creating the Wget startup
2761 file---@file{.wgetrc}.
2763 Besides @file{.wgetrc} is the ``main'' initialization file, it is
2764 convenient to have a special facility for storing passwords. Thus Wget
2765 reads and interprets the contents of @file{$HOME/.netrc}, if it finds
2766 it. You can find @file{.netrc} format in your system manuals.
2768 Wget reads @file{.wgetrc} upon startup, recognizing a limited set of
2772 * Wgetrc Location:: Location of various wgetrc files.
2773 * Wgetrc Syntax:: Syntax of wgetrc.
2774 * Wgetrc Commands:: List of available commands.
2775 * Sample Wgetrc:: A wgetrc example.
2778 @node Wgetrc Location, Wgetrc Syntax, Startup File, Startup File
2779 @section Wgetrc Location
2780 @cindex wgetrc location
2781 @cindex location of wgetrc
2783 When initializing, Wget will look for a @dfn{global} startup file,
2784 @file{/usr/local/etc/wgetrc} by default (or some prefix other than
2785 @file{/usr/local}, if Wget was not installed there) and read commands
2786 from there, if it exists.
2788 Then it will look for the user's file. If the environmental variable
2789 @code{WGETRC} is set, Wget will try to load that file. Failing that, no
2790 further attempts will be made.
2792 If @code{WGETRC} is not set, Wget will try to load @file{$HOME/.wgetrc}.
2794 The fact that user's settings are loaded after the system-wide ones
2795 means that in case of collision user's wgetrc @emph{overrides} the
2796 system-wide wgetrc (in @file{/usr/local/etc/wgetrc} by default).
2797 Fascist admins, away!
2799 @node Wgetrc Syntax, Wgetrc Commands, Wgetrc Location, Startup File
2800 @section Wgetrc Syntax
2801 @cindex wgetrc syntax
2802 @cindex syntax of wgetrc
2804 The syntax of a wgetrc command is simple:
2810 The @dfn{variable} will also be called @dfn{command}. Valid
2811 @dfn{values} are different for different commands.
2813 The commands are case-insensitive and underscore-insensitive. Thus
2814 @samp{DIr__PrefiX} is the same as @samp{dirprefix}. Empty lines, lines
2815 beginning with @samp{#} and lines containing white-space only are
2818 Commands that expect a comma-separated list will clear the list on an
2819 empty command. So, if you wish to reset the rejection list specified in
2820 global @file{wgetrc}, you can do it with:
2826 @node Wgetrc Commands, Sample Wgetrc, Wgetrc Syntax, Startup File
2827 @section Wgetrc Commands
2828 @cindex wgetrc commands
2830 The complete set of commands is listed below. Legal values are listed
2831 after the @samp{=}. Simple Boolean values can be set or unset using
2832 @samp{on} and @samp{off} or @samp{1} and @samp{0}.
2834 Some commands take pseudo-arbitrary values. @var{address} values can be
2835 hostnames or dotted-quad IP addresses. @var{n} can be any positive
2836 integer, or @samp{inf} for infinity, where appropriate. @var{string}
2837 values can be any non-empty string.
2839 Most of these commands have direct command-line equivalents. Also, any
2840 wgetrc command can be specified on the command line using the
2841 @samp{--execute} switch (@pxref{Basic Startup Options}.)
2844 @item accept/reject = @var{string}
2845 Same as @samp{-A}/@samp{-R} (@pxref{Types of Files}).
2847 @item add_hostdir = on/off
2848 Enable/disable host-prefixed file names. @samp{-nH} disables it.
2850 @item ask_password = on/off
2851 Prompt for a password for each connection established. Cannot be specified
2852 when @samp{--password} is being used, because they are mutually
2853 exclusive. Equivalent to @samp{--ask-password}.
2855 @item auth_no_challenge = on/off
2856 If this option is given, Wget will send Basic HTTP authentication
2857 information (plaintext username and password) for all requests. See
2858 @samp{--auth-no-challenge}.
2860 @item background = on/off
2861 Enable/disable going to background---the same as @samp{-b} (which
2864 @item backup_converted = on/off
2865 Enable/disable saving pre-converted files with the suffix
2866 @samp{.orig}---the same as @samp{-K} (which enables it).
2868 @c @item backups = @var{number}
2869 @c #### Document me!
2871 @item base = @var{string}
2872 Consider relative @sc{url}s in input files (specified via the
2873 @samp{input} command or the @samp{--input-file}/@samp{-i} option,
2874 together with @samp{force_html} or @samp{--force-html})
2875 as being relative to @var{string}---the same as @samp{--base=@var{string}}.
2877 @item bind_address = @var{address}
2878 Bind to @var{address}, like the @samp{--bind-address=@var{address}}.
2880 @item ca_certificate = @var{file}
2881 Set the certificate authority bundle file to @var{file}. The same
2882 as @samp{--ca-certificate=@var{file}}.
2884 @item ca_directory = @var{directory}
2885 Set the directory used for certificate authorities. The same as
2886 @samp{--ca-directory=@var{directory}}.
2888 @item cache = on/off
2889 When set to off, disallow server-caching. See the @samp{--no-cache}
2892 @item certificate = @var{file}
2893 Set the client certificate file name to @var{file}. The same as
2894 @samp{--certificate=@var{file}}.
2896 @item certificate_type = @var{string}
2897 Specify the type of the client certificate, legal values being
2898 @samp{PEM} (the default) and @samp{DER} (aka ASN1). The same as
2899 @samp{--certificate-type=@var{string}}.
2901 @item check_certificate = on/off
2902 If this is set to off, the server certificate is not checked against
2903 the specified client authorities. The default is ``on''. The same as
2904 @samp{--check-certificate}.
2906 @item connect_timeout = @var{n}
2907 Set the connect timeout---the same as @samp{--connect-timeout}.
2909 @item content_disposition = on/off
2910 Turn on recognition of the (non-standard) @samp{Content-Disposition}
2911 HTTP header---if set to @samp{on}, the same as @samp{--content-disposition}.
2913 @item trust_server_names = on/off
2914 If set to on, use the last component of a redirection URL for the local
2917 @item continue = on/off
2918 If set to on, force continuation of preexistent partially retrieved
2919 files. See @samp{-c} before setting it.
2921 @item convert_links = on/off
2922 Convert non-relative links locally. The same as @samp{-k}.
2924 @item cookies = on/off
2925 When set to off, disallow cookies. See the @samp{--cookies} option.
2927 @item cut_dirs = @var{n}
2928 Ignore @var{n} remote directory components. Equivalent to
2929 @samp{--cut-dirs=@var{n}}.
2931 @item debug = on/off
2932 Debug mode, same as @samp{-d}.
2934 @item default_page = @var{string}
2935 Default page name---the same as @samp{--default-page=@var{string}}.
2937 @item delete_after = on/off
2938 Delete after download---the same as @samp{--delete-after}.
2940 @item dir_prefix = @var{string}
2941 Top of directory tree---the same as @samp{-P @var{string}}.
2943 @item dirstruct = on/off
2944 Turning dirstruct on or off---the same as @samp{-x} or @samp{-nd},
2947 @item dns_cache = on/off
2948 Turn DNS caching on/off. Since DNS caching is on by default, this
2949 option is normally used to turn it off and is equivalent to
2950 @samp{--no-dns-cache}.
2952 @item dns_timeout = @var{n}
2953 Set the DNS timeout---the same as @samp{--dns-timeout}.
2955 @item domains = @var{string}
2956 Same as @samp{-D} (@pxref{Spanning Hosts}).
2958 @item dot_bytes = @var{n}
2959 Specify the number of bytes ``contained'' in a dot, as seen throughout
2960 the retrieval (1024 by default). You can postfix the value with
2961 @samp{k} or @samp{m}, representing kilobytes and megabytes,
2962 respectively. With dot settings you can tailor the dot retrieval to
2963 suit your needs, or you can use the predefined @dfn{styles}
2964 (@pxref{Download Options}).
2966 @item dot_spacing = @var{n}
2967 Specify the number of dots in a single cluster (10 by default).
2969 @item dots_in_line = @var{n}
2970 Specify the number of dots that will be printed in each line throughout
2971 the retrieval (50 by default).
2973 @item egd_file = @var{file}
2974 Use @var{string} as the EGD socket file name. The same as
2975 @samp{--egd-file=@var{file}}.
2977 @item exclude_directories = @var{string}
2978 Specify a comma-separated list of directories you wish to exclude from
2979 download---the same as @samp{-X @var{string}} (@pxref{Directory-Based
2982 @item exclude_domains = @var{string}
2983 Same as @samp{--exclude-domains=@var{string}} (@pxref{Spanning
2986 @item follow_ftp = on/off
2987 Follow @sc{ftp} links from @sc{html} documents---the same as
2988 @samp{--follow-ftp}.
2990 @item follow_tags = @var{string}
2991 Only follow certain @sc{html} tags when doing a recursive retrieval,
2992 just like @samp{--follow-tags=@var{string}}.
2994 @item force_html = on/off
2995 If set to on, force the input filename to be regarded as an @sc{html}
2996 document---the same as @samp{-F}.
2998 @item ftp_password = @var{string}
2999 Set your @sc{ftp} password to @var{string}. Without this setting, the
3000 password defaults to @samp{-wget@@}, which is a useful default for
3001 anonymous @sc{ftp} access.
3003 This command used to be named @code{passwd} prior to Wget 1.10.
3005 @item ftp_proxy = @var{string}
3006 Use @var{string} as @sc{ftp} proxy, instead of the one specified in
3009 @item ftp_user = @var{string}
3010 Set @sc{ftp} user to @var{string}.
3012 This command used to be named @code{login} prior to Wget 1.10.
3015 Turn globbing on/off---the same as @samp{--glob} and @samp{--no-glob}.
3017 @item header = @var{string}
3018 Define a header for HTTP downloads, like using
3019 @samp{--header=@var{string}}.
3021 @item adjust_extension = on/off
3022 Add a @samp{.html} extension to @samp{text/html} or
3023 @samp{application/xhtml+xml} files that lack one, or a @samp{.css}
3024 extension to @samp{text/css} files that lack one, like
3025 @samp{-E}. Previously named @samp{html_extension} (still acceptable,
3028 @item http_keep_alive = on/off
3029 Turn the keep-alive feature on or off (defaults to on). Turning it
3030 off is equivalent to @samp{--no-http-keep-alive}.
3032 @item http_password = @var{string}
3033 Set @sc{http} password, equivalent to
3034 @samp{--http-password=@var{string}}.
3036 @item http_proxy = @var{string}
3037 Use @var{string} as @sc{http} proxy, instead of the one specified in
3040 @item http_user = @var{string}
3041 Set @sc{http} user to @var{string}, equivalent to
3042 @samp{--http-user=@var{string}}.
3044 @item https_proxy = @var{string}
3045 Use @var{string} as @sc{https} proxy, instead of the one specified in
3048 @item ignore_case = on/off
3049 When set to on, match files and directories case insensitively; the
3050 same as @samp{--ignore-case}.
3052 @item ignore_length = on/off
3053 When set to on, ignore @code{Content-Length} header; the same as
3054 @samp{--ignore-length}.
3056 @item ignore_tags = @var{string}
3057 Ignore certain @sc{html} tags when doing a recursive retrieval, like
3058 @samp{--ignore-tags=@var{string}}.
3060 @item include_directories = @var{string}
3061 Specify a comma-separated list of directories you wish to follow when
3062 downloading---the same as @samp{-I @var{string}}.
3065 When set to on, enable internationalized URI (IRI) support; the same as
3068 @item inet4_only = on/off
3069 Force connecting to IPv4 addresses, off by default. You can put this
3070 in the global init file to disable Wget's attempts to resolve and
3071 connect to IPv6 hosts. Available only if Wget was compiled with IPv6
3072 support. The same as @samp{--inet4-only} or @samp{-4}.
3074 @item inet6_only = on/off
3075 Force connecting to IPv6 addresses, off by default. Available only if
3076 Wget was compiled with IPv6 support. The same as @samp{--inet6-only}
3079 @item input = @var{file}
3080 Read the @sc{url}s from @var{string}, like @samp{-i @var{file}}.
3082 @item keep_session_cookies = on/off
3083 When specified, causes @samp{save_cookies = on} to also save session
3084 cookies. See @samp{--keep-session-cookies}.
3086 @item limit_rate = @var{rate}
3087 Limit the download speed to no more than @var{rate} bytes per second.
3088 The same as @samp{--limit-rate=@var{rate}}.
3090 @item load_cookies = @var{file}
3091 Load cookies from @var{file}. See @samp{--load-cookies @var{file}}.
3093 @item local_encoding = @var{encoding}
3094 Force Wget to use @var{encoding} as the default system encoding. See
3095 @samp{--local-encoding}.
3097 @item logfile = @var{file}
3098 Set logfile to @var{file}, the same as @samp{-o @var{file}}.
3100 @item max_redirect = @var{number}
3101 Specifies the maximum number of redirections to follow for a resource.
3102 See @samp{--max-redirect=@var{number}}.
3104 @item mirror = on/off
3105 Turn mirroring on/off. The same as @samp{-m}.
3107 @item netrc = on/off
3108 Turn reading netrc on or off.
3110 @item no_clobber = on/off
3113 @item no_parent = on/off
3114 Disallow retrieving outside the directory hierarchy, like
3115 @samp{--no-parent} (@pxref{Directory-Based Limits}).
3117 @item no_proxy = @var{string}
3118 Use @var{string} as the comma-separated list of domains to avoid in
3119 proxy loading, instead of the one specified in environment.
3121 @item output_document = @var{file}
3122 Set the output filename---the same as @samp{-O @var{file}}.
3124 @item page_requisites = on/off
3125 Download all ancillary documents necessary for a single @sc{html} page to
3126 display properly---the same as @samp{-p}.
3128 @item passive_ftp = on/off
3129 Change setting of passive @sc{ftp}, equivalent to the
3130 @samp{--passive-ftp} option.
3132 @item password = @var{string}
3133 Specify password @var{string} for both @sc{ftp} and @sc{http} file retrieval.
3134 This command can be overridden using the @samp{ftp_password} and
3135 @samp{http_password} command for @sc{ftp} and @sc{http} respectively.
3137 @item post_data = @var{string}
3138 Use POST as the method for all HTTP requests and send @var{string} in
3139 the request body. The same as @samp{--post-data=@var{string}}.
3141 @item post_file = @var{file}
3142 Use POST as the method for all HTTP requests and send the contents of
3143 @var{file} in the request body. The same as
3144 @samp{--post-file=@var{file}}.
3146 @item prefer_family = none/IPv4/IPv6
3147 When given a choice of several addresses, connect to the addresses
3148 with specified address family first. The address order returned by
3149 DNS is used without change by default. The same as @samp{--prefer-family},
3150 which see for a detailed discussion of why this is useful.
3152 @item private_key = @var{file}
3153 Set the private key file to @var{file}. The same as
3154 @samp{--private-key=@var{file}}.
3156 @item private_key_type = @var{string}
3157 Specify the type of the private key, legal values being @samp{PEM}
3158 (the default) and @samp{DER} (aka ASN1). The same as
3159 @samp{--private-type=@var{string}}.
3161 @item progress = @var{string}
3162 Set the type of the progress indicator. Legal types are @samp{dot}
3163 and @samp{bar}. Equivalent to @samp{--progress=@var{string}}.
3165 @item protocol_directories = on/off
3166 When set, use the protocol name as a directory component of local file
3167 names. The same as @samp{--protocol-directories}.
3169 @item proxy_password = @var{string}
3170 Set proxy authentication password to @var{string}, like
3171 @samp{--proxy-password=@var{string}}.
3173 @item proxy_user = @var{string}
3174 Set proxy authentication user name to @var{string}, like
3175 @samp{--proxy-user=@var{string}}.
3177 @item quiet = on/off
3178 Quiet mode---the same as @samp{-q}.
3180 @item quota = @var{quota}
3181 Specify the download quota, which is useful to put in the global
3182 @file{wgetrc}. When download quota is specified, Wget will stop
3183 retrieving after the download sum has become greater than quota. The
3184 quota can be specified in bytes (default), kbytes @samp{k} appended) or
3185 mbytes (@samp{m} appended). Thus @samp{quota = 5m} will set the quota
3186 to 5 megabytes. Note that the user's startup file overrides system
3189 @item random_file = @var{file}
3190 Use @var{file} as a source of randomness on systems lacking
3193 @item random_wait = on/off
3194 Turn random between-request wait times on or off. The same as
3195 @samp{--random-wait}.
3197 @item read_timeout = @var{n}
3198 Set the read (and write) timeout---the same as
3199 @samp{--read-timeout=@var{n}}.
3201 @item reclevel = @var{n}
3202 Recursion level (depth)---the same as @samp{-l @var{n}}.
3204 @item recursive = on/off
3205 Recursive on/off---the same as @samp{-r}.
3207 @item referer = @var{string}
3208 Set HTTP @samp{Referer:} header just like
3209 @samp{--referer=@var{string}}. (Note that it was the folks who wrote
3210 the @sc{http} spec who got the spelling of ``referrer'' wrong.)
3212 @item relative_only = on/off
3213 Follow only relative links---the same as @samp{-L} (@pxref{Relative
3216 @item remote_encoding = @var{encoding}
3217 Force Wget to use @var{encoding} as the default remote server encoding.
3218 See @samp{--remote-encoding}.
3220 @item remove_listing = on/off
3221 If set to on, remove @sc{ftp} listings downloaded by Wget. Setting it
3222 to off is the same as @samp{--no-remove-listing}.
3224 @item restrict_file_names = unix/windows
3225 Restrict the file names generated by Wget from URLs. See
3226 @samp{--restrict-file-names} for a more detailed description.
3228 @item retr_symlinks = on/off
3229 When set to on, retrieve symbolic links as if they were plain files; the
3230 same as @samp{--retr-symlinks}.
3232 @item retry_connrefused = on/off
3233 When set to on, consider ``connection refused'' a transient
3234 error---the same as @samp{--retry-connrefused}.
3236 @item robots = on/off
3237 Specify whether the norobots convention is respected by Wget, ``on'' by
3238 default. This switch controls both the @file{/robots.txt} and the
3239 @samp{nofollow} aspect of the spec. @xref{Robot Exclusion}, for more
3240 details about this. Be sure you know what you are doing before turning
3243 @item save_cookies = @var{file}
3244 Save cookies to @var{file}. The same as @samp{--save-cookies
3247 @item save_headers = on/off
3248 Same as @samp{--save-headers}.
3250 @item secure_protocol = @var{string}
3251 Choose the secure protocol to be used. Legal values are @samp{auto}
3252 (the default), @samp{SSLv2}, @samp{SSLv3}, and @samp{TLSv1}. The same
3253 as @samp{--secure-protocol=@var{string}}.
3255 @item server_response = on/off
3256 Choose whether or not to print the @sc{http} and @sc{ftp} server
3257 responses---the same as @samp{-S}.
3259 @item show_all_dns_entries = on/off
3260 When a DNS name is resolved, show all the IP addresses, not just the first
3263 @item span_hosts = on/off
3266 @item spider = on/off
3267 Same as @samp{--spider}.
3269 @item strict_comments = on/off
3270 Same as @samp{--strict-comments}.
3272 @item timeout = @var{n}
3273 Set all applicable timeout values to @var{n}, the same as @samp{-T
3276 @item timestamping = on/off
3277 Turn timestamping on/off. The same as @samp{-N} (@pxref{Time-Stamping}).
3279 @item use_server_timestamps = on/off
3280 If set to @samp{off}, Wget won't set the local file's timestamp by the
3281 one on the server (same as @samp{--no-use-server-timestamps}).
3283 @item tries = @var{n}
3284 Set number of retries per @sc{url}---the same as @samp{-t @var{n}}.
3286 @item use_proxy = on/off
3287 When set to off, don't use proxy even when proxy-related environment
3288 variables are set. In that case it is the same as using
3291 @item user = @var{string}
3292 Specify username @var{string} for both @sc{ftp} and @sc{http} file retrieval.
3293 This command can be overridden using the @samp{ftp_user} and
3294 @samp{http_user} command for @sc{ftp} and @sc{http} respectively.
3296 @item user_agent = @var{string}
3297 User agent identification sent to the HTTP Server---the same as
3298 @samp{--user-agent=@var{string}}.
3300 @item verbose = on/off
3301 Turn verbose on/off---the same as @samp{-v}/@samp{-nv}.
3303 @item wait = @var{n}
3304 Wait @var{n} seconds between retrievals---the same as @samp{-w
3307 @item wait_retry = @var{n}
3308 Wait up to @var{n} seconds between retries of failed retrievals
3309 only---the same as @samp{--waitretry=@var{n}}. Note that this is
3310 turned on by default in the global @file{wgetrc}.
3313 @node Sample Wgetrc, , Wgetrc Commands, Startup File
3314 @section Sample Wgetrc
3315 @cindex sample wgetrc
3317 This is the sample initialization file, as given in the distribution.
3318 It is divided in two section---one for global usage (suitable for global
3319 startup file), and one for local usage (suitable for
3320 @file{$HOME/.wgetrc}). Be careful about the things you change.
3322 Note that almost all the lines are commented out. For a command to have
3323 any effect, you must remove the @samp{#} character at the beginning of
3327 @include sample.wgetrc.munged_for_texi_inclusion
3330 @node Examples, Various, Startup File, Top
3334 @c man begin EXAMPLES
3335 The examples are divided into three sections loosely based on their
3339 * Simple Usage:: Simple, basic usage of the program.
3340 * Advanced Usage:: Advanced tips.
3341 * Very Advanced Usage:: The hairy stuff.
3344 @node Simple Usage, Advanced Usage, Examples, Examples
3345 @section Simple Usage
3349 Say you want to download a @sc{url}. Just type:
3352 wget http://fly.srk.fer.hr/
3356 But what will happen if the connection is slow, and the file is lengthy?
3357 The connection will probably fail before the whole file is retrieved,
3358 more than once. In this case, Wget will try getting the file until it
3359 either gets the whole of it, or exceeds the default number of retries
3360 (this being 20). It is easy to change the number of tries to 45, to
3361 insure that the whole file will arrive safely:
3364 wget --tries=45 http://fly.srk.fer.hr/jpg/flyweb.jpg
3368 Now let's leave Wget to work in the background, and write its progress
3369 to log file @file{log}. It is tiring to type @samp{--tries}, so we
3370 shall use @samp{-t}.
3373 wget -t 45 -o log http://fly.srk.fer.hr/jpg/flyweb.jpg &
3376 The ampersand at the end of the line makes sure that Wget works in the
3377 background. To unlimit the number of retries, use @samp{-t inf}.
3380 The usage of @sc{ftp} is as simple. Wget will take care of login and
3384 wget ftp://gnjilux.srk.fer.hr/welcome.msg
3388 If you specify a directory, Wget will retrieve the directory listing,
3389 parse it and convert it to @sc{html}. Try:
3392 wget ftp://ftp.gnu.org/pub/gnu/
3397 @node Advanced Usage, Very Advanced Usage, Simple Usage, Examples
3398 @section Advanced Usage
3402 You have a file that contains the URLs you want to download? Use the
3409 If you specify @samp{-} as file name, the @sc{url}s will be read from
3413 Create a five levels deep mirror image of the GNU web site, with the
3414 same directory structure the original has, with only one try per
3415 document, saving the log of the activities to @file{gnulog}:
3418 wget -r http://www.gnu.org/ -o gnulog
3422 The same as the above, but convert the links in the downloaded files to
3423 point to local files, so you can view the documents off-line:
3426 wget --convert-links -r http://www.gnu.org/ -o gnulog
3430 Retrieve only one @sc{html} page, but make sure that all the elements needed
3431 for the page to be displayed, such as inline images and external style
3432 sheets, are also downloaded. Also make sure the downloaded page
3433 references the downloaded links.
3436 wget -p --convert-links http://www.server.com/dir/page.html
3439 The @sc{html} page will be saved to @file{www.server.com/dir/page.html}, and
3440 the images, stylesheets, etc., somewhere under @file{www.server.com/},
3441 depending on where they were on the remote server.
3444 The same as the above, but without the @file{www.server.com/} directory.
3445 In fact, I don't want to have all those random server directories
3446 anyway---just save @emph{all} those files under a @file{download/}
3447 subdirectory of the current directory.
3450 wget -p --convert-links -nH -nd -Pdownload \
3451 http://www.server.com/dir/page.html
3455 Retrieve the index.html of @samp{www.lycos.com}, showing the original
3459 wget -S http://www.lycos.com/
3463 Save the server headers with the file, perhaps for post-processing.
3466 wget --save-headers http://www.lycos.com/
3471 Retrieve the first two levels of @samp{wuarchive.wustl.edu}, saving them
3475 wget -r -l2 -P/tmp ftp://wuarchive.wustl.edu/
3479 You want to download all the @sc{gif}s from a directory on an @sc{http}
3480 server. You tried @samp{wget http://www.server.com/dir/*.gif}, but that
3481 didn't work because @sc{http} retrieval does not support globbing. In
3485 wget -r -l1 --no-parent -A.gif http://www.server.com/dir/
3488 More verbose, but the effect is the same. @samp{-r -l1} means to
3489 retrieve recursively (@pxref{Recursive Download}), with maximum depth
3490 of 1. @samp{--no-parent} means that references to the parent directory
3491 are ignored (@pxref{Directory-Based Limits}), and @samp{-A.gif} means to
3492 download only the @sc{gif} files. @samp{-A "*.gif"} would have worked
3496 Suppose you were in the middle of downloading, when Wget was
3497 interrupted. Now you do not want to clobber the files already present.
3501 wget -nc -r http://www.gnu.org/
3505 If you want to encode your own username and password to @sc{http} or
3506 @sc{ftp}, use the appropriate @sc{url} syntax (@pxref{URL Format}).
3509 wget ftp://hniksic:mypassword@@unix.server.com/.emacs
3512 Note, however, that this usage is not advisable on multi-user systems
3513 because it reveals your password to anyone who looks at the output of
3516 @cindex redirecting output
3518 You would like the output documents to go to standard output instead of
3522 wget -O - http://jagor.srce.hr/ http://www.srce.hr/
3525 You can also combine the two options and make pipelines to retrieve the
3526 documents from remote hotlists:
3529 wget -O - http://cool.list.com/ | wget --force-html -i -
3533 @node Very Advanced Usage, , Advanced Usage, Examples
3534 @section Very Advanced Usage
3539 If you wish Wget to keep a mirror of a page (or @sc{ftp}
3540 subdirectories), use @samp{--mirror} (@samp{-m}), which is the shorthand
3541 for @samp{-r -l inf -N}. You can put Wget in the crontab file asking it
3542 to recheck a site each Sunday:
3546 0 0 * * 0 wget --mirror http://www.gnu.org/ -o /home/me/weeklog
3550 In addition to the above, you want the links to be converted for local
3551 viewing. But, after having read this manual, you know that link
3552 conversion doesn't play well with timestamping, so you also want Wget to
3553 back up the original @sc{html} files before the conversion. Wget invocation
3554 would look like this:
3557 wget --mirror --convert-links --backup-converted \
3558 http://www.gnu.org/ -o /home/me/weeklog
3562 But you've also noticed that local viewing doesn't work all that well
3563 when @sc{html} files are saved under extensions other than @samp{.html},
3564 perhaps because they were served as @file{index.cgi}. So you'd like
3565 Wget to rename all the files served with content-type @samp{text/html}
3566 or @samp{application/xhtml+xml} to @file{@var{name}.html}.
3569 wget --mirror --convert-links --backup-converted \
3570 --html-extension -o /home/me/weeklog \
3574 Or, with less typing:
3577 wget -m -k -K -E http://www.gnu.org/ -o /home/me/weeklog
3582 @node Various, Appendices, Examples, Top
3586 This chapter contains all the stuff that could not fit anywhere else.
3589 * Proxies:: Support for proxy servers.
3590 * Distribution:: Getting the latest version.
3591 * Web Site:: GNU Wget's presence on the World Wide Web.
3592 * Mailing Lists:: Wget mailing list for announcements and discussion.
3593 * Internet Relay Chat:: Wget's presence on IRC.
3594 * Reporting Bugs:: How and where to report bugs.
3595 * Portability:: The systems Wget works on.
3596 * Signals:: Signal-handling performed by Wget.
3599 @node Proxies, Distribution, Various, Various
3603 @dfn{Proxies} are special-purpose @sc{http} servers designed to transfer
3604 data from remote servers to local clients. One typical use of proxies
3605 is lightening network load for users behind a slow connection. This is
3606 achieved by channeling all @sc{http} and @sc{ftp} requests through the
3607 proxy which caches the transferred data. When a cached resource is
3608 requested again, proxy will return the data from cache. Another use for
3609 proxies is for companies that separate (for security reasons) their
3610 internal networks from the rest of Internet. In order to obtain
3611 information from the Web, their users connect and retrieve remote data
3612 using an authorized proxy.
3614 @c man begin ENVIRONMENT
3615 Wget supports proxies for both @sc{http} and @sc{ftp} retrievals. The
3616 standard way to specify proxy location, which Wget recognizes, is using
3617 the following environment variables:
3622 If set, the @env{http_proxy} and @env{https_proxy} variables should
3623 contain the @sc{url}s of the proxies for @sc{http} and @sc{https}
3624 connections respectively.
3627 This variable should contain the @sc{url} of the proxy for @sc{ftp}
3628 connections. It is quite common that @env{http_proxy} and
3629 @env{ftp_proxy} are set to the same @sc{url}.
3632 This variable should contain a comma-separated list of domain extensions
3633 proxy should @emph{not} be used for. For instance, if the value of
3634 @env{no_proxy} is @samp{.mit.edu}, proxy will not be used to retrieve
3639 In addition to the environment variables, proxy location and settings
3640 may be specified from within Wget itself.
3644 @itemx proxy = on/off
3645 This option and the corresponding command may be used to suppress the
3646 use of proxy, even if the appropriate environment variables are set.
3648 @item http_proxy = @var{URL}
3649 @itemx https_proxy = @var{URL}
3650 @itemx ftp_proxy = @var{URL}
3651 @itemx no_proxy = @var{string}
3652 These startup file variables allow you to override the proxy settings
3653 specified by the environment.
3656 Some proxy servers require authorization to enable you to use them. The
3657 authorization consists of @dfn{username} and @dfn{password}, which must
3658 be sent by Wget. As with @sc{http} authorization, several
3659 authentication schemes exist. For proxy authorization only the
3660 @code{Basic} authentication scheme is currently implemented.
3662 You may specify your username and password either through the proxy
3663 @sc{url} or through the command-line options. Assuming that the
3664 company's proxy is located at @samp{proxy.company.com} at port 8001, a
3665 proxy @sc{url} location containing authorization data might look like
3669 http://hniksic:mypassword@@proxy.company.com:8001/
3672 Alternatively, you may use the @samp{proxy-user} and
3673 @samp{proxy-password} options, and the equivalent @file{.wgetrc}
3674 settings @code{proxy_user} and @code{proxy_password} to set the proxy
3675 username and password.
3677 @node Distribution, Web Site, Proxies, Various
3678 @section Distribution
3679 @cindex latest version
3681 Like all GNU utilities, the latest version of Wget can be found at the
3682 master GNU archive site ftp.gnu.org, and its mirrors. For example,
3683 Wget @value{VERSION} can be found at
3684 @url{ftp://ftp.gnu.org/pub/gnu/wget/wget-@value{VERSION}.tar.gz}
3686 @node Web Site, Mailing Lists, Distribution, Various
3690 The official web site for GNU Wget is at
3691 @url{http://www.gnu.org/software/wget/}. However, most useful
3692 information resides at ``The Wget Wgiki'',
3693 @url{http://wget.addictivecode.org/}.
3695 @node Mailing Lists, Internet Relay Chat, Web Site, Various
3696 @section Mailing Lists
3697 @cindex mailing list
3700 @unnumberedsubsec Primary List
3702 The primary mailinglist for discussion, bug-reports, or questions
3703 about GNU Wget is at @email{bug-wget@@gnu.org}. To subscribe, send an
3704 email to @email{bug-wget-join@@gnu.org}, or visit
3705 @url{http://lists.gnu.org/mailman/listinfo/bug-wget}.
3707 You do not need to subscribe to send a message to the list; however,
3708 please note that unsubscribed messages are moderated, and may take a
3709 while before they hit the list---@strong{usually around a day}. If
3710 you want your message to show up immediately, please subscribe to the
3711 list before posting. Archives for the list may be found at
3712 @url{http://lists.gnu.org/pipermail/bug-wget/}.
3714 An NNTP/Usenettish gateway is also available via
3715 @uref{http://gmane.org/about.php,Gmane}. You can see the Gmane
3717 @url{http://news.gmane.org/gmane.comp.web.wget.general}. Note that the
3718 Gmane archives conveniently include messages from both the current
3719 list, and the previous one. Messages also show up in the Gmane
3720 archives sooner than they do at @url{lists.gnu.org}.
3722 @unnumberedsubsec Bug Notices List
3724 Additionally, there is the @email{wget-notify@@addictivecode.org} mailing
3725 list. This is a non-discussion list that receives bug report
3726 notifications from the bug-tracker. To subscribe to this list,
3727 send an email to @email{wget-notify-join@@addictivecode.org},
3728 or visit @url{http://addictivecode.org/mailman/listinfo/wget-notify}.
3730 @unnumberedsubsec Obsolete Lists
3732 Previously, the mailing list @email{wget@@sunsite.dk} was used as the
3733 main discussion list, and another list,
3734 @email{wget-patches@@sunsite.dk} was used for submitting and
3735 discussing patches to GNU Wget.
3737 Messages from @email{wget@@sunsite.dk} are archived at
3740 @url{http://www.mail-archive.com/wget%40sunsite.dk/} and at
3742 @url{http://news.gmane.org/gmane.comp.web.wget.general} (which also
3743 continues to archive the current list, @email{bug-wget@@gnu.org}).
3746 Messages from @email{wget-patches@@sunsite.dk} are archived at
3749 @url{http://news.gmane.org/gmane.comp.web.wget.patches}.
3752 @node Internet Relay Chat, Reporting Bugs, Mailing Lists, Various
3753 @section Internet Relay Chat
3754 @cindex Internet Relay Chat
3758 In addition to the mailinglists, we also have a support channel set up
3759 via IRC at @code{irc.freenode.org}, @code{#wget}. Come check it out!
3761 @node Reporting Bugs, Portability, Internet Relay Chat, Various
3762 @section Reporting Bugs
3764 @cindex reporting bugs
3768 You are welcome to submit bug reports via the GNU Wget bug tracker (see
3769 @url{http://wget.addictivecode.org/BugTracker}).
3771 Before actually submitting a bug report, please try to follow a few
3776 Please try to ascertain that the behavior you see really is a bug. If
3777 Wget crashes, it's a bug. If Wget does not behave as documented,
3778 it's a bug. If things work strange, but you are not sure about the way
3779 they are supposed to work, it might well be a bug, but you might want to
3780 double-check the documentation and the mailing lists (@pxref{Mailing
3784 Try to repeat the bug in as simple circumstances as possible. E.g. if
3785 Wget crashes while downloading @samp{wget -rl0 -kKE -t5 --no-proxy
3786 http://yoyodyne.com -o /tmp/log}, you should try to see if the crash is
3787 repeatable, and if will occur with a simpler set of options. You might
3788 even try to start the download at the page where the crash occurred to
3789 see if that page somehow triggered the crash.
3791 Also, while I will probably be interested to know the contents of your
3792 @file{.wgetrc} file, just dumping it into the debug message is probably
3793 a bad idea. Instead, you should first try to see if the bug repeats
3794 with @file{.wgetrc} moved out of the way. Only if it turns out that
3795 @file{.wgetrc} settings affect the bug, mail me the relevant parts of
3799 Please start Wget with @samp{-d} option and send us the resulting
3800 output (or relevant parts thereof). If Wget was compiled without
3801 debug support, recompile it---it is @emph{much} easier to trace bugs
3802 with debug support on.
3804 Note: please make sure to remove any potentially sensitive information
3805 from the debug log before sending it to the bug address. The
3806 @code{-d} won't go out of its way to collect sensitive information,
3807 but the log @emph{will} contain a fairly complete transcript of Wget's
3808 communication with the server, which may include passwords and pieces
3809 of downloaded data. Since the bug address is publically archived, you
3810 may assume that all bug reports are visible to the public.
3813 If Wget has crashed, try to run it in a debugger, e.g. @code{gdb `which
3814 wget` core} and type @code{where} to get the backtrace. This may not
3815 work if the system administrator has disabled core files, but it is
3820 @node Portability, Signals, Reporting Bugs, Various
3821 @section Portability
3823 @cindex operating systems
3825 Like all GNU software, Wget works on the GNU system. However, since it
3826 uses GNU Autoconf for building and configuring, and mostly avoids using
3827 ``special'' features of any particular Unix, it should compile (and
3828 work) on all common Unix flavors.
3830 Various Wget versions have been compiled and tested under many kinds of
3831 Unix systems, including GNU/Linux, Solaris, SunOS 4.x, Mac OS X, OSF
3832 (aka Digital Unix or Tru64), Ultrix, *BSD, IRIX, AIX, and others. Some
3833 of those systems are no longer in widespread use and may not be able to
3834 support recent versions of Wget. If Wget fails to compile on your
3835 system, we would like to know about it.
3837 Thanks to kind contributors, this version of Wget compiles and works
3838 on 32-bit Microsoft Windows platforms. It has been compiled
3839 successfully using MS Visual C++ 6.0, Watcom, Borland C, and GCC
3840 compilers. Naturally, it is crippled of some features available on
3841 Unix, but it should work as a substitute for people stuck with
3842 Windows. Note that Windows-specific portions of Wget are not
3843 guaranteed to be supported in the future, although this has been the
3844 case in practice for many years now. All questions and problems in
3845 Windows usage should be reported to Wget mailing list at
3846 @email{wget@@sunsite.dk} where the volunteers who maintain the
3847 Windows-related features might look at them.
3849 Support for building on MS-DOS via DJGPP has been contributed by Gisle
3850 Vanem; a port to VMS is maintained by Steven Schweda, and is available
3851 at @url{http://antinode.org/}.
3853 @node Signals, , Portability, Various
3855 @cindex signal handling
3858 Since the purpose of Wget is background work, it catches the hangup
3859 signal (@code{SIGHUP}) and ignores it. If the output was on standard
3860 output, it will be redirected to a file named @file{wget-log}.
3861 Otherwise, @code{SIGHUP} is ignored. This is convenient when you wish
3862 to redirect the output of Wget after having started it.
3865 $ wget http://www.gnus.org/dist/gnus.tar.gz &
3868 SIGHUP received, redirecting output to `wget-log'.
3871 Other than that, Wget will not try to interfere with signals in any way.
3872 @kbd{C-c}, @code{kill -TERM} and @code{kill -KILL} should kill it alike.
3874 @node Appendices, Copying this manual, Various, Top
3877 This chapter contains some references I consider useful.
3880 * Robot Exclusion:: Wget's support for RES.
3881 * Security Considerations:: Security with Wget.
3882 * Contributors:: People who helped.
3885 @node Robot Exclusion, Security Considerations, Appendices, Appendices
3886 @section Robot Exclusion
3887 @cindex robot exclusion
3889 @cindex server maintenance
3891 It is extremely easy to make Wget wander aimlessly around a web site,
3892 sucking all the available data in progress. @samp{wget -r @var{site}},
3893 and you're set. Great? Not for the server admin.
3895 As long as Wget is only retrieving static pages, and doing it at a
3896 reasonable rate (see the @samp{--wait} option), there's not much of a
3897 problem. The trouble is that Wget can't tell the difference between the
3898 smallest static page and the most demanding CGI. A site I know has a
3899 section handled by a CGI Perl script that converts Info files to @sc{html} on
3900 the fly. The script is slow, but works well enough for human users
3901 viewing an occasional Info file. However, when someone's recursive Wget
3902 download stumbles upon the index page that links to all the Info files
3903 through the script, the system is brought to its knees without providing
3904 anything useful to the user (This task of converting Info files could be
3905 done locally and access to Info documentation for all installed GNU
3906 software on a system is available from the @code{info} command).
3908 To avoid this kind of accident, as well as to preserve privacy for
3909 documents that need to be protected from well-behaved robots, the
3910 concept of @dfn{robot exclusion} was invented. The idea is that
3911 the server administrators and document authors can specify which
3912 portions of the site they wish to protect from robots and those
3913 they will permit access.
3915 The most popular mechanism, and the @i{de facto} standard supported by
3916 all the major robots, is the ``Robots Exclusion Standard'' (RES) written
3917 by Martijn Koster et al. in 1994. It specifies the format of a text
3918 file containing directives that instruct the robots which URL paths to
3919 avoid. To be found by the robots, the specifications must be placed in
3920 @file{/robots.txt} in the server root, which the robots are expected to
3923 Although Wget is not a web robot in the strictest sense of the word, it
3924 can download large parts of the site without the user's intervention to
3925 download an individual page. Because of that, Wget honors RES when
3926 downloading recursively. For instance, when you issue:
3929 wget -r http://www.server.com/
3932 First the index of @samp{www.server.com} will be downloaded. If Wget
3933 finds that it wants to download more documents from that server, it will
3934 request @samp{http://www.server.com/robots.txt} and, if found, use it
3935 for further downloads. @file{robots.txt} is loaded only once per each
3938 Until version 1.8, Wget supported the first version of the standard,
3939 written by Martijn Koster in 1994 and available at
3940 @url{http://www.robotstxt.org/wc/norobots.html}. As of version 1.8,
3941 Wget has supported the additional directives specified in the internet
3942 draft @samp{<draft-koster-robots-00.txt>} titled ``A Method for Web
3943 Robots Control''. The draft, which has as far as I know never made to
3944 an @sc{rfc}, is available at
3945 @url{http://www.robotstxt.org/wc/norobots-rfc.txt}.
3947 This manual no longer includes the text of the Robot Exclusion Standard.
3949 The second, less known mechanism, enables the author of an individual
3950 document to specify whether they want the links from the file to be
3951 followed by a robot. This is achieved using the @code{META} tag, like
3955 <meta name="robots" content="nofollow">
3958 This is explained in some detail at
3959 @url{http://www.robotstxt.org/wc/meta-user.html}. Wget supports this
3960 method of robot exclusion in addition to the usual @file{/robots.txt}
3963 If you know what you are doing and really really wish to turn off the
3964 robot exclusion, set the @code{robots} variable to @samp{off} in your
3965 @file{.wgetrc}. You can achieve the same effect from the command line
3966 using the @code{-e} switch, e.g. @samp{wget -e robots=off @var{url}...}.
3968 @node Security Considerations, Contributors, Robot Exclusion, Appendices
3969 @section Security Considerations
3972 When using Wget, you must be aware that it sends unencrypted passwords
3973 through the network, which may present a security problem. Here are the
3974 main issues, and some solutions.
3978 The passwords on the command line are visible using @code{ps}. The best
3979 way around it is to use @code{wget -i -} and feed the @sc{url}s to
3980 Wget's standard input, each on a separate line, terminated by @kbd{C-d}.
3981 Another workaround is to use @file{.netrc} to store passwords; however,
3982 storing unencrypted passwords is also considered a security risk.
3985 Using the insecure @dfn{basic} authentication scheme, unencrypted
3986 passwords are transmitted through the network routers and gateways.
3989 The @sc{ftp} passwords are also in no way encrypted. There is no good
3990 solution for this at the moment.
3993 Although the ``normal'' output of Wget tries to hide the passwords,
3994 debugging logs show them, in all forms. This problem is avoided by
3995 being careful when you send debug logs (yes, even when you send them to
3999 @node Contributors, , Security Considerations, Appendices
4000 @section Contributors
4001 @cindex contributors
4004 GNU Wget was written by Hrvoje Nik@v{s}i@'{c} @email{hniksic@@xemacs.org},
4007 GNU Wget was written by Hrvoje Niksic @email{hniksic@@xemacs.org}.
4010 However, the development of Wget could never have gone as far as it has, were
4011 it not for the help of many people, either with bug reports, feature proposals,
4012 patches, or letters saying ``Thanks!''.
4014 Special thanks goes to the following people (no particular order):
4017 @item Dan Harkless---contributed a lot of code and documentation of
4018 extremely high quality, as well as the @code{--page-requisites} and
4019 related options. He was the principal maintainer for some time and
4022 @item Ian Abbott---contributed bug fixes, Windows-related fixes, and
4023 provided a prototype implementation of the breadth-first recursive
4024 download. Co-maintained Wget during the 1.8 release cycle.
4027 The dotsrc.org crew, in particular Karsten Thygesen---donated system
4028 resources such as the mailing list, web space, @sc{ftp} space, and
4029 version control repositories, along with a lot of time to make these
4030 actually work. Christian Reiniger was of invaluable help with setting
4034 Heiko Herold---provided high-quality Windows builds and contributed
4035 bug and build reports for many years.
4038 Shawn McHorse---bug reports and patches.
4041 Kaveh R. Ghazi---on-the-fly @code{ansi2knr}-ization. Lots of
4045 Gordon Matzigkeit---@file{.netrc} support.
4049 Zlatko @v{C}alu@v{s}i@'{c}, Tomislav Vujec and Dra@v{z}en
4050 Ka@v{c}ar---feature suggestions and ``philosophical'' discussions.
4053 Zlatko Calusic, Tomislav Vujec and Drazen Kacar---feature suggestions
4054 and ``philosophical'' discussions.
4058 Darko Budor---initial port to Windows.
4061 Antonio Rosella---help and suggestions, plus the initial Italian
4066 Tomislav Petrovi@'{c}, Mario Miko@v{c}evi@'{c}---many bug reports and
4070 Tomislav Petrovic, Mario Mikocevic---many bug reports and suggestions.
4075 Fran@,{c}ois Pinard---many thorough bug reports and discussions.
4078 Francois Pinard---many thorough bug reports and discussions.
4082 Karl Eichwalder---lots of help with internationalization, Makefile
4083 layout and many other things.
4086 Junio Hamano---donated support for Opie and @sc{http} @code{Digest}
4090 Mauro Tortonesi---improved IPv6 support, adding support for dual
4091 family systems. Refactored and enhanced FTP IPv6 code. Maintained GNU
4092 Wget from 2004--2007.
4095 Christopher G.@: Lewis---maintenance of the Windows version of GNU WGet.
4098 Gisle Vanem---many helpful patches and improvements, especially for
4099 Windows and MS-DOS support.
4102 Ralf Wildenhues---contributed patches to convert Wget to use Automake as
4103 part of its build process, and various bugfixes.
4106 Steven Schubiger---Many helpful patches, bugfixes and improvements.
4107 Notably, conversion of Wget to use the Gnulib quotes and quoteargs
4108 modules, and the addition of password prompts at the console, via the
4109 Gnulib getpasswd-gnu module.
4112 Ted Mielczarek---donated support for CSS.
4115 Saint Xavier---Support for IRIs (RFC 3987).
4118 People who provided donations for development---including Brian Gough.
4121 The following people have provided patches, bug/build reports, useful
4122 suggestions, beta testing services, fan mail and all the other things
4123 that make maintenance so much fun:
4143 Kristijan @v{C}onka@v{s},
4152 Bertrand Demiddelaer,
4153 Alexander Dergachev,
4166 Aleksandar Erkalovi@'{c},
4169 Aleksandar Erkalovic,
4193 Madhusudan Hosaagrahara,
4197 Erik Magnus Hulthen,
4216 Goran Kezunovi@'{c},
4230 $\Sigma\acute{\iota}\mu o\varsigma\;
4231 \Xi\varepsilon\nu\iota\tau\acute{\epsilon}\lambda\lambda\eta\varsigma$
4232 (Simos KSenitellis),
4241 Nicol@'{a}s Lichtmeier,
4247 Alexander V.@: Lukyanov,
4256 Matthew J.@: Mellon,
4292 @c Texinfo doesn't grok @'{@i}, so we have to use TeX itself.
4294 Juan Jos\'{e} Rodr\'{\i}guez,
4297 Juan Jose Rodriguez,
4299 Maciej W.@: Rozycki,
4306 Steven M.@: Schweda,
4317 Szakacsits Szabolcs,
4332 Douglas E.@: Wegscheid,
4334 Joshua David Williams,
4348 Apologies to all who I accidentally left out, and many thanks to all the
4349 subscribers of the Wget mailing list.
4351 @node Copying this manual, Concept Index, Appendices, Top
4352 @appendix Copying this manual
4355 * GNU Free Documentation License:: Licnse for copying this manual.
4358 @node GNU Free Documentation License, , Copying this manual, Copying this manual
4359 @appendixsec GNU Free Documentation License
4360 @cindex FDL, GNU Free Documentation License
4365 @node Concept Index, , Copying this manual, Top
4366 @unnumbered Concept Index