README.asciidoc 10 KB

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