README.asciidoc 12 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337
  1. aria2 - The ultra fast download utility
  2. =======================================
  3. :Author: Tatsuhiro Tsujikawa
  4. :Email: t-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. The project page is located at http://aria2.sourceforge.net/.
  20. See http://aria2.sourceforge.net/aria2c.1.html[aria2 Online Manual]
  21. and http://sourceforge.net/apps/trac/aria2/wiki/UsageExample[the usage
  22. example] to learn how to use aria2.
  23. Features
  24. --------
  25. Here is a list of features:
  26. * Command-line interface
  27. * Download files through HTTP(S)/FTP/BitTorrent
  28. * Segmented downloading
  29. * Metalink version 4 (RFC 5854) support(HTTP/FTP/BitTorrent)
  30. * Metalink version 3.0 support(HTTP/FTP/BitTorrent)
  31. * Metalink/HTTP (RFC 6249) support
  32. * HTTP/1.1 implementation
  33. * HTTP Proxy support
  34. * HTTP BASIC authentication support
  35. * HTTP Proxy authentication support
  36. * Well-known environment variables for proxy: http_proxy, https_proxy,
  37. ftp_proxy, all_proxy and no_proxy
  38. * HTTP gzip, deflate content encoding support
  39. * Verify peer using given trusted CA certificate in HTTPS
  40. * Client certificate authentication in HTTPS
  41. * Chunked transfer encoding support
  42. * Load Cookies from file using the Firefox3 format, Chromium/Google Chrome
  43. and the Mozilla/Firefox
  44. (1.x/2.x)/Netscape format.
  45. * Save Cookies in the Mozilla/Firefox (1.x/2.x)/Netscape format.
  46. * Custom HTTP Header support
  47. * Persistent Connections support
  48. * FTP through HTTP Proxy
  49. * Download/Upload speed throttling
  50. * BitTorrent extensions: Fast extension, DHT, PEX, MSE/PSE, Multi-Tracker
  51. * BitTorrent http://getright.com/seedtorrent.html[WEB-Seeding]. aria2
  52. requests chunks more than piece size to reduce the request
  53. overhead. It also supports pipelined requests with piece size.
  54. * BitTorrent Local Peer Discovery
  55. * Rename/change the directory structure of BitTorrent downloads
  56. completely
  57. * JSON-RPC (over HTTP and WebSocket)/XML-RPC interface
  58. * Run as a daemon process
  59. * Selective download in multi-file torrent/Metalink
  60. * Chunk checksum validation in Metalink
  61. * Can disable segmented downloading in Metalink
  62. * Netrc support
  63. * Configuration file support
  64. * Download URIs found in a text file or stdin and the destination directory and
  65. output filename can be specified optionally
  66. * Parameterized URI support
  67. * IPv6 support
  68. How to get source code
  69. ----------------------
  70. We maintain the source code at Github:
  71. https://github.com/tatsuhiro-t/aria2
  72. To download the latest source code, run following command:
  73. ------------------------------------------------
  74. git clone git://github.com/tatsuhiro-t/aria2.git
  75. ------------------------------------------------
  76. This will create aria2 directory in your current directory and source
  77. files are stored there.
  78. Dependency
  79. ----------
  80. .External Library Dependency
  81. [options="header"]
  82. |==================================================================
  83. |features |dependency
  84. |HTTPS |GnuTLS or OpenSSL
  85. |BitTorrent |libnettle+libgmp or libgcrypt or OpenSSL
  86. |Metalink |libxml2 or Expat.
  87. |Checksum |libnettle or libgcrypt or OpenSSL
  88. |gzip, deflate in HTTP |zlib
  89. |Async DNS |C-Ares
  90. |Firefox3/Chromium cookie|libsqlite3
  91. |XML-RPC |libxml2 or Expat.
  92. |JSON-RPC over WebSocket |libnettle or libgcrypt or OpenSSL
  93. |==================================================================
  94. Note;;
  95. libxml2 has precedence over Expat if both libraries are installed.
  96. If you prefer Expat, run configure with \--without-libxml2.
  97. Note;;
  98. GnuTLS has precedence over OpenSSL if both libraries are installed.
  99. If you prefer OpenSSL, run configure with \--without-gnutls
  100. \--with-openssl.
  101. Note;;
  102. libnettle has precedence over libgcrypt if both libraries are
  103. installed. If you prefer libgcrypt, run configure with
  104. \--without-libnettle \--with-libgcrypt. If OpenSSL is selected over
  105. GnuTLS, neither libnettle nor libgcrypt will be used.
  106. A user can have one of the following configurations for SSL and crypto
  107. libraries:
  108. * libgcrypt
  109. * libnettle
  110. * OpenSSL
  111. * GnuTLS + libgcrypt
  112. * GnuTLS + libnettle
  113. You can disable BitTorrent, Metalink support by providing
  114. \--disable-bittorrent, \--disable-metalink respectively to configure
  115. script.
  116. In order to enable async DNS support, you need c-ares.
  117. * c-ares: http://daniel.haxx.se/projects/c-ares/
  118. How to build
  119. ------------
  120. In order to build aria2 from the source package, you need following
  121. development packages(package name may vary depending on the
  122. distribution you use):
  123. * libgnutls-dev (Required for HTTPS, BitTorrent, Checksum support)
  124. * nettle-dev (Required for BitTorrent, Checksum support)
  125. * libgmp-dev (Required for BitTorrent)
  126. * libc-ares-dev (Required for async DNS support)
  127. * libxml2-dev (Required for Metalink support)
  128. * zlib1g-dev (Required for gzip, deflate decoding support in HTTP)
  129. * libsqlite3-dev (Required for Firefox3/Chromium cookie support)
  130. You can use libgcrypt-dev instead of nettle-dev and libgmp-dev:
  131. * libgpg-error-dev (Required for BitTorrent, Checksum support)
  132. * libgcrypt-dev (Required for BitTorrent, Checksum support)
  133. You can use libssl-dev instead of
  134. libgnutls-dev, nettle-dev, libgmp-dev, libgpg-error-dev and libgcrypt-dev:
  135. * libssl-dev (Required for HTTPS, BitTorrent, Checksum support)
  136. You can use libexpat1-dev instead of libxml2-dev:
  137. * libexpat1-dev (Required for Metalink support)
  138. You may also need pkg-config to detect the above mentioned libraries.
  139. On Fedora you need the following packages:
  140. gcc, gcc-c++, kernel-devel, libgcrypt-devel, libgcrypt-devel, libxml2-devel, openssl-devel
  141. If you downloaded source code from git repository, you have to run
  142. following command to generate configure script and other files
  143. necessary to build the program:
  144. ---------------
  145. $ autoreconf -i
  146. ---------------
  147. If you are building aria2 for Mac OS X, take a look at
  148. build_osx_release.sh, which builds OSX universal binary DMG.
  149. The quickest way to build aria2 is just type following commands:
  150. -------------
  151. $ ./configure
  152. $ make
  153. -------------
  154. The configure script checks available libraries and enables the features
  155. as much as possible because all the features are enabled by default.
  156. Since 1.1.0, aria2 checks the certificate of HTTPS servers by default.
  157. If you build with HTTPS support, I recommend to supply the path to the
  158. CA bundle file. For example, in Debian the path to CA bundle file is
  159. '/etc/ssl/certs/ca-certificates.crt' (in ca-certificates package). This
  160. may vary depending on your distribution. You can give it to
  161. configure script using \--with-ca-bundle option:
  162. -------------------------------------------------------------------
  163. $ ./configure --with-ca-bundle='/etc/ssl/certs/ca-certificates.crt'
  164. $ make
  165. -------------------------------------------------------------------
  166. Without \--with-ca-bundle option, you will encounter the error when
  167. accessing HTTPS servers because the certificate cannot be verified
  168. without CA bundle. In such case, you can specify the CA bundle file
  169. using aria2's \--ca-certificate option. If you don't have CA bundle
  170. file installed, then the last resort is disable the certificate
  171. validation using \--check-certificate=false.
  172. The executable is 'aria2c' in src directory.
  173. aria2 uses CppUnit for automated unit testing. To run the unit test:
  174. ------------
  175. $ make check
  176. ------------
  177. BitTorrrent
  178. -----------
  179. About filename
  180. ~~~~~~~~~~~~~~
  181. The filename of the downloaded file is determined as follows:
  182. single-file mode::
  183. If "name" key is present in .torrent file, filename is the value
  184. of "name" key. Otherwise, filename is the basename of .torrent
  185. file appended by ".file". For example, .torrent file is
  186. "test.torrrent", then filename is "test.torrent.file". The
  187. directory to store the downloaded file can be specified by -d
  188. option.
  189. multi-file mode::
  190. The complete directory/file structure mentioned in .torrent file
  191. is created. The directory to store the top directory of
  192. downloaded files can be specified by -d option.
  193. Before download starts, a complete directory structure is created if
  194. needed. By default, aria2 opens at most 100 files mentioned in
  195. .torrent file, and directly writes to and reads from these files.
  196. The number of files to open simultaneously can be controlled by
  197. \--bt-max-open-files option.
  198. DHT
  199. ~~~
  200. aria2 supports mainline compatible DHT. By default, the routing table
  201. for IPv4 DHT is saved to $HOME/.aria2/dht.dat and the routing table
  202. for IPv6 DHT is saved to $HOME/.aria2/dht6.dat. aria2 uses same port
  203. number to listen on for both IPv4 and IPv6 DHT.
  204. Other things should be noted
  205. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  206. * -o option is used to change the filename of .torrent file itself,
  207. not a filename of a file in .torrent file. For this purpose, use
  208. --index-out option instead.
  209. * The port numbers that aria2 uses by default are 6881-6999 for TCP
  210. and UDP.
  211. * aria2 doesn't configure port-forwarding automatically. Please
  212. configure your router or firewall manually.
  213. * The maximum number of peers is 55. This limit may be exceeded when
  214. download rate is low. This download rate can be adjusted using
  215. \--bt-request-peer-speed-limit option.
  216. * As of release 0.10.0, aria2 stops sending request message after
  217. selective download completes.
  218. Metalink
  219. --------
  220. The current implementation supports HTTP(S)/FTP/BitTorrent. The other
  221. P2P protocols are ignored. Both Metalink4 and Metalink version 3.0
  222. documents are supported.
  223. For checksum verification, md5, sha-1, sha-224, sha-256, sha-384 and
  224. sha-512 are supported. If multiple hash algorithms are provided, aria2
  225. uses stronger one. If whole file checksum verification fails, aria2
  226. doesn't retry the download and just exits with non-zero return code.
  227. The supported user preferences are version, language, location,
  228. protocol and os.
  229. If chunk checksums are provided in Metalink file, aria2 automatically
  230. validates chunks of data during download. This behavior can be turned
  231. off by a command-line option.
  232. If signature is included in a Metalink file, aria2 saves it as a file
  233. after the completion of the download. The filename is download
  234. filename + ".sig". If same file already exists, the signature file is
  235. not saved.
  236. In Metalink4, multi-file torrent could appear in metalink:metaurl
  237. element. Since aria2 cannot download 2 same torrents at the same
  238. time, aria2 groups files in metalink:file element which has same
  239. BitTorrent metaurl and downloads them from a single BitTorrent swarm.
  240. This is basically multi-file torrent download with file selection, so
  241. the adjacent files which is not in Metalink document but shares same
  242. piece with selected file are also created.
  243. If relative URI is specified in metalink:url or metalink:metaurl
  244. element, aria2 uses the URI of Metalink file as base URI to resolve
  245. the relative URI. If relative URI is found in Metalink file which is
  246. read from local disk, aria2 uses the value of --metalink-base-uri
  247. option as base URI. If this option is not specified, the relative URI
  248. will be ignored.
  249. Metalink/HTTP
  250. -------------
  251. The current implementation only uses rel=duplicate links only. aria2
  252. understands Digest header fields and check whether it matches the
  253. digest value from other sources. If it differs, drop connection.
  254. aria2 also uses this digest value to perform checksum verification
  255. after download finished. aria2 recognizes geo value. To tell aria2
  256. which location you prefer, you can use --metalink-location option.
  257. netrc
  258. -----
  259. netrc support is enabled by default for HTTP(S)/FTP. To disable netrc
  260. support, specify -n command-line option. Your .netrc file should have
  261. correct permissions(600).
  262. References
  263. ----------
  264. * http://aria2.sourceforge.net/aria2c.1.html[aria2 Online Manual]
  265. * http://aria2.sourceforge.net/
  266. * http://sourceforge.net/apps/trac/aria2/wiki
  267. * https://github.com/tatsuhiro-t/aria2
  268. * http://tools.ietf.org/html/rfc5854
  269. * http://tools.ietf.org/html/rfc6249
  270. * http://tools.ietf.org/html/rfc6455