README 8.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228
  1. aria2 - The ultra fast download utility
  2. =======================================
  3. :Author: Tatsuhiro Tsujikawa
  4. :Email: tujikawa_at_users_dot_sourceforge_dot_net
  5. Disclaimer
  6. ----------
  7. This program comes with no warranty.
  8. You must use this program at your own risk.
  9. Introduction
  10. ------------
  11. aria2 is a utility for downloading files. The supported protocols are
  12. HTTP(S), FTP, BitTorrent, and Metalink. aria2 can download a file from
  13. multiple sources/protocols and tries to utilize your maximum download
  14. bandwidth. It supports downloading a file from HTTP(S)/FTP and
  15. BitTorrent at the same time, while the data downloaded from
  16. HTTP(S)/FTP is uploaded to the BitTorrent swarm. Using Metalink's
  17. chunk checksums, aria2 automatically validates chunks of data while
  18. downloading a file like BitTorrent.
  19. Here is a list of features.
  20. * Command-line interface
  21. * Download files through HTTP(S)/FTP/BitTorrent
  22. * Segmented downloading
  23. * Metalink version 3.0 support(HTTP/FTP/BitTorrent)
  24. * HTTP/1.1 implementation
  25. * HTTP Proxy support
  26. * HTTP BASIC authentication support
  27. * HTTP Proxy authentication support
  28. * Well-known environment variables for proxy: http_proxy, https_proxy,
  29. ftp_proxy, all_proxy and no_proxy
  30. * HTTP gzip, deflate content encoding support
  31. * Verify peer using given trusted CA certificate in HTTPS
  32. * Client certificate authentication in HTTPS
  33. * Chunked transfer encoding support
  34. * Load Cookies from file using the Firefox3 format and the Mozilla/Firefox
  35. (1.x/2.x)/Netscape format.
  36. * Custom HTTP Header support
  37. * Persistent Connections support
  38. * FTP through HTTP Proxy
  39. * Download/Upload speed throttling
  40. * BitTorrent extensions: Fast extension, DHT, PEX, MSE/PSE, Multi-Tracker
  41. * BitTorrent http://getright.com/seedtorrent.html[WEB-Seeding]
  42. (single-file torrent only)
  43. * Rename/change the directory structure of BitTorrent downloads
  44. completely
  45. * Run as a daemon process
  46. * Selective download in multi-file torrent/Metalink
  47. * Chunk checksum validation in Metalink
  48. * Can disable segmented downloading in Metalink
  49. * Netrc support
  50. * Configuration file support
  51. * Download URIs found in a text file or stdin and the destination directory and
  52. output filename can be specified optionally
  53. * Parameterized URI support
  54. Dependency
  55. ----------
  56. .External Library Dependency
  57. [frame="all", grid="all"]
  58. `--------------------`---------------------------
  59. features dependency
  60. -------------------------------------------------
  61. HTTPS GnuTLS or OpenSSL
  62. BitTorrent GnuTLS+Libgcrypt or OpenSSL
  63. Metalink libxml2 or Expat.
  64. Checksum GnuTLS+Libgcrypt or OpenSSL
  65. gzip, deflate in HTTP zlib
  66. Async DNS C-Ares
  67. Firefox3 cookie libsqlite3
  68. -------------------------------------------------
  69. Note;;
  70. GNU TLS has precedence over OpenSSL if both libraries are installed.
  71. If you prefer OpenSSL, run configure with \--without-gnutls.
  72. Note;;
  73. libxml2 has precedence over Expat if both libraries are installed.
  74. If you prefer Expat, run configure with \--without-libxml2.
  75. You can disable BitTorrent, Metalink support by providing
  76. \--disable-bittorrent, \--disable-metalink respectively to configure
  77. script.
  78. In order to enable async DNS support, you need c-ares.
  79. * c-ares: http://daniel.haxx.se/projects/c-ares/
  80. How to build
  81. ------------
  82. In order to build aria2 from the source package, you need following
  83. development packages(package name may vary depending on the
  84. distribution you use):
  85. * libgnutls-dev (Required for HTTPS, BitTorrent, Checksum support)
  86. * libgpg-error-dev (Required for BitTorrent, Checksum support)
  87. * libgcrypt-dev (Required for BitTorrent, Checksum support)
  88. * libc-ares-dev (Required for async DNS support)
  89. * libxml2-dev (Required for Metalink support)
  90. * libz1g-dev (Required for gzip, deflate decoding support in HTTP)
  91. * libsqlite3-dev (Required for Firefox3 cookie support)
  92. You can use libssl-dev instead of
  93. libgnutls-dev,libgpg-error-dev,libgcrypt-dev:
  94. * libssl-dev (Required for HTTPS, BitTorrent, Checksum support)
  95. You can use libexpat1-dev instead of libxml2-dev:
  96. * libexpat1-dev (Required for Metalink support)
  97. The quickest way to build aria2 is just type following commands:
  98. -------------
  99. $ ./configure
  100. $ make
  101. -------------
  102. The configure script checks available libraries and enables the features
  103. as much as possible because all the features are enabled by default.
  104. Since 1.1.0, aria2 checks the certificate of HTTPS servers by default.
  105. If you build with HTTPS support, I recommend to supply the path to the
  106. CA bundle file. For example, in Debian the path to CA bundle file is
  107. '/etc/ssl/certs/ca-certificates.crt' (in ca-certificates package). This
  108. may vary depending on your distribution. You can give it to
  109. configure script using \--with-ca-bundle option:
  110. -------------------------------------------------------------------
  111. $ ./configure --with-ca-bundle='/etc/ssl/certs/ca-certificates.crt'
  112. $ make
  113. -------------------------------------------------------------------
  114. Without \--with-ca-bundle option, you will encounter the error when
  115. accessing HTTPS servers because the certificate cannot be verified
  116. without CA bundle. In such case, you can specify the CA bundle file
  117. using aria2's \--ca-certificate option. If you don't have CA bundle
  118. file installed, then the last resort is disable the certificate
  119. validation using \--check-certificate=false.
  120. The executable is 'aria2c' in src directory.
  121. aria2 uses CppUnit for automated unit testing. To run the unit test:
  122. ------------
  123. $ make check
  124. ------------
  125. BitTorrrent
  126. -----------
  127. About filename
  128. ~~~~~~~~~~~~~~
  129. The filename of the downloaded file is determined as follows:
  130. single-file mode::
  131. If "name" key is present in .torrent file, filename is the value
  132. of "name" key. Otherwise, filename is the basename of .torrent
  133. file appended by ".file". For example, .torrent file is
  134. "test.torrrent", then filename is "test.torrent.file". The
  135. directory to store the downloaded file can be specified by -d
  136. option.
  137. multi-file mode::
  138. The complete directory/file structure mentioned in .torrent file
  139. is created. The directory to store the top directory of
  140. downloaded files can be specified by -d option.
  141. Before download starts, a complete directory structure is created if
  142. needed. By default, aria2 opens at most 100 files mentioned in
  143. .torrent file, and directly writes to and reads from these files.
  144. The number of files to open simultaneously can be controlled by
  145. \--bt-max-open-files option.
  146. DHT
  147. ~~~
  148. As of release 0.13.0, aria2 supports DHT. By default, the routing
  149. table is saved to $HOME/.aria2/dht.dat.
  150. Other things should be noted
  151. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  152. * -o option is used to change the filename of .torrent file itself,
  153. not a filename of a file in .torrent file.
  154. * The port numbers that aria2 uses by default are 6881-6999 for TCP
  155. and UDP.
  156. * aria2 doesn't configure port-forwarding automatically. Please
  157. configure your router or firewall manually.
  158. * The maximum number of peers is 55. This limit may be exceeded when
  159. download rate is low. This download rate can be adjusted using
  160. \--bt-request-peer-speed-limit option.
  161. * As of release 0.10.0, aria2 stops sending request message after
  162. selective download completes.
  163. Metalink
  164. --------
  165. The current implementation supports HTTP(S)/FTP/BitTorrent. The other
  166. P2P protocols are ignored.
  167. For checksum verification, MD5, SHA1, and SHA256 are supported. If
  168. multiple hash algorithms are provided, aria2 uses SHA1. If whole file
  169. checksum verification fails, aria2 doesn't retry the download and just
  170. exits with non-zero return code.
  171. The supported user preferences are version, language, location,
  172. protocol and os.
  173. If chunk checksums are provided in Metalink file, aria2 automatically
  174. validates chunks of data during download. This behavior can be turned
  175. off by a command-line option.
  176. If signature is included in a Metalink file, aria2 saves it as a file
  177. after the completion of the download. The filename is download
  178. filename + ".sig". If same file already exists, the signature file is
  179. not saved.
  180. netrc
  181. -----
  182. netrc support is enabled by default for HTTP(S)/FTP. To disable netrc
  183. support, specify -n command-line option. Your .netrc file should have
  184. correct permissions(600).
  185. References
  186. ----------
  187. * man aria2c
  188. * http://aria2.sourceforge.net/
  189. * http://apps.sourceforge.net/trac/aria2/wiki