GNU Wget

Rating: 
5
Your rating: None Average: 5 (3 votes)

GNU Wget is a free utility for non-interactive download of files from the Web. It supports HTTP, HTTPS, and FTP protocols, as well as retrieval through HTTP proxies.

Source code for create your builds.

This chapter is a partial overview of Wget’s features.

  • Wget is non-interactive, meaning that it can work in the background, while the user is not logged on. This allows you to start a retrieval and disconnect from the system, letting Wget finish the work. By contrast, most of the Web browsers require constant user’s presence, which can be a great hindrance when transferring a lot of data.
  • Wget can follow links in HTML, XHTML, and CSS pages, to create local versions of remote web sites, fully recreating the directory structure of the original site. This is sometimes referred to as “recursive downloading.” While doing that, Wget respects the Robot Exclusion Standard (/robots.txt). Wget can be instructed to convert the links in downloaded files to point at the local files, for offline viewing.
  • File name wildcard matching and recursive mirroring of directories are available when retrieving via FTP. Wget can read the time-stamp information given by both HTTP and FTP servers, and store it locally. Thus Wget can see if the remote file has changed since last retrieval, and automatically retrieve the new version if it has. This makes Wget suitable for mirroring of FTP sites, as well as home pages.
  • Wget has been designed for robustness over slow or unstable network connections; if a download fails due to a network problem, it will keep retrying until the whole file has been retrieved. If the server supports regetting, it will instruct the server to continue the download from where it left off.
  • Wget supports proxy servers, which can lighten the network load, speed up retrieval and provide access behind firewalls. Wget uses the passive FTP downloading by default, active FTP being an option.
  • Wget supports IP version 6, the next generation of IP. IPv6 is autodetected at compile-time, and can be disabled at either build or run time. Binaries built with IPv6 support work well in both IPv4-only and dual family environments.
  • Built-in features offer mechanisms to tune which links you wish to follow (see Following Links).
  • The progress of individual downloads is traced using a progress gauge. Interactive downloads are tracked using a “thermometer”-style gauge, whereas non-interactive ones are traced with dots, each dot representing a fixed amount of data received (1KB by default). Either gauge can be customized to your preferences.
  • Most of the features are fully configurable, either through command line options, or via the initialization file .wgetrc (see Startup File). Wget allows you to define global startup files (/usr/local/etc/wgetrc by default) for site settings. You can also specify the location of a startup file with the –config option.
  • Finally, GNU Wget is free software. This means that everyone may use it, redistribute it and/or modify it under the terms of the GNU General Public License, as published by the Free Software Foundation (see the file COPYING that came with GNU Wget, for details).
Screenshots: 
Application versions: 
AttachmentSizeDate
File wget-1.18-1.armv7hl.rpm566.14 KB11/06/2016 - 11:47
File wget-1.19-1.armv7hl.rpm620.18 KB10/02/2017 - 03:54
Changelog: 

GNU Wget 1.19:

New option --use-askpass=COMMAND. Fetch user/password by calling
  an external program.

Use IDNA2008 (+ TR46 if available) through libidn2

When processing a Metalink header, --metalink-index=<number> allows
  to process the header's application/metalink4+xml files.

When processing a Metalink file, --trust-server-names enables the
  use of the destination file names specified in the Metalink file,
  otherwise a safe destination file name is computed.

When processing a Metalink file, enforce a safe destination path.
  Remove any drive letter prefix under w32, i.e. 'C:D:file'.  Call
  libmetalink's metalink_check_safe_path() to prevent absolute,
  relative, or home paths:
  https://tools.ietf.org/html/rfc5854#section-4.1.2.1
  https://tools.ietf.org/html/rfc5854#section-4.2.8.3

When processing a Metalink file, --directory-prefix=<prefix> sets
  the top of the retrieval tree to prefix for Metalink downloads.

When processing a Metalink file, reject downloaded files which don't
  agree with their own metalink:size value:
  https://tools.ietf.org/html/rfc5854#section-4.2.16

When processing a Metalink file, with --continue resume partially
  downloaded files and keep fully downloaded files even if they fail
  the verification.

When processing a Metalink file, create the parent directories of a
  "path/file" destination file name:
  https://tools.ietf.org/html/rfc5854#section-4.1.2.1
  https://tools.ietf.org/html/rfc5854#section-4.2.8.3

On a recursive download, append a .tmp suffix to temporary files
  that will be deleted after being parsed, and create them
  readable/writable only by the owner.

New make target 'check-valgrind'

Fix several bugs

Fix compatibility issues

 

GNU Wget 1.18:

By default, on server redirects to a FTP resource, use the original
  URL to get the local file name. Close CVE-2016-4971.  This
  introduces a backward-incompatibility for HTTP->FTP redirects and
  any script that relies on the old  behaviour must use
  --trust-server-names.
Check the HSTS file is not world-writable before using it.
Parse <img srcset> attributes on a recursive download.
Fix problem with SNI server names having trailing dot(s).
New options --bind-dns-address and --dns-servers.
When Wget is built with libiconv, it now converts non-ASCII URIs to
  the locale's codeset when it creates files.  The encoding of the
  remote files and URIs is taken from --remote-encoding, defaulting to
  UTF-8.  The result is that non-ASCII URIs and files downloaded via
  HTTP/HTTPS and FTP will have names on the local filesystem that
  correspond to their remote names.