README 8.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253
  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. * Run as a daemon process
  42. * Selective download in multi-file torrent/Metalink
  43. * Chunk checksum validation in Metalink
  44. * Can disable segmented downloading in Metalink
  45. * Netrc support
  46. * Configuration file support
  47. * Download URIs found in a text file or stdin and the destination directory and
  48. output filename can be specified optionally
  49. * Parameterized URI support
  50. Dependency
  51. ----------
  52. .External Library Dependency
  53. [frame="all", grid="all"]
  54. `--------------------`---------------------------
  55. features dependency
  56. -------------------------------------------------
  57. HTTPS GnuTLS or OpenSSL
  58. BitTorrent GnuTLS+Libgcrypt or OpenSSL
  59. Metalink libxml2 or Expat.
  60. Checksum GnuTLS+Libgcrypt or OpenSSL
  61. gzip, deflate in HTTP zlib
  62. Async DNS C-Ares
  63. Firefox3 cookie libsqlite3
  64. -------------------------------------------------
  65. Note;;
  66. GNU TLS has precedence over OpenSSL if both libraries are installed.
  67. If you prefer OpenSSL, run configure with "--without-gnutls".
  68. Note;;
  69. libxml2 has precedence over Expat if both libraries are installed.
  70. If you prefer Expat, run configure with "--without-libxml2".
  71. You can disable BitTorrent, Metalink support by providing
  72. --disable-bittorrent, --disable-metalink respectively to configure
  73. script.
  74. In order to enable async DNS support, you need c-ares.
  75. * c-ares: http://daniel.haxx.se/projects/c-ares/
  76. How to build
  77. ------------
  78. In order to build aria2 from the source package, you need following
  79. development packages(package name may vary depending on the
  80. distribution you use):
  81. * libgnutls-dev (Required for HTTPS, BitTorrent, Checksum support)
  82. * libgpg-error-dev (Required for BitTorrent, Checksum support)
  83. * libgcrypt-dev (Required for BitTorrent, Checksum support)
  84. * libc-ares-dev (Required for async DNS support)
  85. * libxml2-dev (Required for Metalink support)
  86. * libz1g-dev (Required for gzip, deflate decoding support in HTTP)
  87. * libsqlite3-dev (Required for Firefox3 cookie support)
  88. You can use libssl-dev instead of
  89. libgnutls-dev,libgpg-error-dev,libgcrypt-dev:
  90. * libssl-dev (Required for HTTPS, BitTorrent, Checksum support)
  91. You can use libexpat1-dev instead of libxml2-dev:
  92. * libexpat1-dev (Required for Metalink support)
  93. The build process is fairly standard way for *nix programs:
  94. -------------
  95. $ ./configure
  96. $ make
  97. -------------
  98. The executable is aria2c in src directory.
  99. aria2 uses CppUnit for automated unit testing. To run run the unit test:
  100. ------------
  101. $ make check
  102. ------------
  103. BitTorrrent
  104. -----------
  105. About filename
  106. ~~~~~~~~~~~~~~
  107. The filename of the downloaded file is determined as follows:
  108. single-file mode::
  109. If "name" key is present in .torrent file, filename is the value
  110. of "name" key. Otherwise, filename is the basename of .torrent
  111. file appended by ".file". For example, .torrent file is
  112. "test.torrrent", then filename is "test.torrent.file". The
  113. directory to store the downloaded file can be specified by -d
  114. option.
  115. multi-file mode::
  116. The complete directory/file structure mentioned in .torrent file
  117. is created. The directory to store the top directory of
  118. downloaded files can be specified by -d option.
  119. In the default behavior, before download starts, a complete directory
  120. structure is created if needed. By default, aria2 opens at most 100
  121. files mentioned in .torrent file, directly writes to and reads from
  122. these files. The number of files to open simultaneously can be
  123. controlled by "--bt-max-open-files" option.
  124. If "--direct-file-mapping" option set to be false, aria2 creates
  125. temporary file in the store directory. The length of this file is the
  126. sum of length of the files in .torrent file, so at least 2 times more
  127. disk space than the file size itself is required. Writing and reading
  128. are done against this file. After download completes, aria2 creates
  129. complete directory structure if needed, and copies whole file or a
  130. part of it to the destination.
  131. DHT
  132. ~~~
  133. As of release 0.13.0, aria2 supports DHT. By default, the routing
  134. table is saved to $HOME/.aria2/dht.dat.
  135. Other things should be noted
  136. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  137. * -o option is used to change the filename of .torrent file itself,
  138. not a filename of a file in .torrent file.
  139. * The port numbers that aria2 uses by default are 6881-6999 for TCP
  140. and UDP.
  141. * aria2 doesn't configure port-forwarding automatically. Please
  142. configure your router or firewall manually.
  143. * The maximum number of peers is 55. This limit may be exceeded when
  144. download rate is low. This download rate can be adjusted using
  145. --bt-request-peer-speed-limit option.
  146. * As of release 0.10.0, aria2 stops sending request message after
  147. selective download completes.
  148. Metalink
  149. --------
  150. The current implementation supports HTTP(S)/FTP/BitTorrent. The other
  151. P2P protocols are ignored.
  152. For checksum checking, MD5, SHA1, SHA256 are supported. If multiple
  153. hash algorithms are provided, aria2 uses SHA1. If checksum checking is
  154. failed, aria2 doesn't retry the download and just exits with non-zero
  155. return code.
  156. The supported user preferences are version, language, location,
  157. protocol and os.
  158. If chunk checksums are provided in Metalink file, aria2 automatically
  159. validates chunks of data during download. This behavior can be turned
  160. off by a command-line option.
  161. If signature is included in a Metalink file, aria2 saves it as a file
  162. after the completion of the download. The filename is download
  163. filename + ".sig". If same file already exists, the signature file is
  164. not saved.
  165. netrc
  166. -----
  167. netrc support is enabled by default for HTTP(S)/FTP. To disable netrc
  168. support, specify -n command-line option. Your .netrc file should have
  169. correct permissions(600).
  170. SERVER PERFORMANCE PROFILE
  171. --------------------------
  172. This section describes the format of server performance profile. The
  173. file is plain text and each line has several NAME=VALUE pair,
  174. delimited by comma. Currently following NAMEs are recognized:
  175. host::
  176. Hostname of the server. Required.
  177. protocol::
  178. Protocol for this profile, such as ftp, http. Required.
  179. dl_speed::
  180. The average download speed observed in the previous download in
  181. bytes per sec. Required.
  182. last_updated::
  183. Last contact time in GMT with this server, specified in the seconds
  184. from the Epoch. Required.
  185. status::
  186. ERROR is set when server cannot be reached or out-of-service or
  187. timeout occurred. Otherwise, OK is set.
  188. Those fields must exist in one line. The order of the fields is not
  189. significant. You can put pairs other than above but they are simply
  190. ignored.
  191. An example is follow:
  192. --------------------------------------------------------------------------------
  193. host=localhost, protocol=http, dl_speed=32000, last_updated=1222491640, status=OK
  194. host=localhost, protocol=ftp, dl_speed=0, last_updated=1222491632, status=ERROR
  195. --------------------------------------------------------------------------------
  196. Configuration file
  197. ------------------
  198. Configuration file must be placed under $HOME/.aria2 and must be named
  199. as aria2.conf. In each line, there is 1 parameter whose syntax is
  200. name=value pair, where name is the long command-line option name
  201. without '--' prefix. The lines beginning '#' are treated as comments.
  202. Example:
  203. --------------------------------------
  204. # sample configuration file for aria2c
  205. listen-port=60000
  206. seed-ratio=1.0
  207. max-upload-limit=40K
  208. ---------------------------------------