1 ==========================
2 The Tahoe REST-ful Web API
3 ==========================
5 1. `Enabling the web-API port`_
6 2. `Basic Concepts: GET, PUT, DELETE, POST`_
11 4. `Slow Operations, Progress, and Cancelling`_
12 5. `Programmatic Operations`_
15 2. `Writing/Uploading a File`_
16 3. `Creating a New Directory`_
17 4. `Getting Information About A File Or Directory (as JSON)`_
18 5. `Attaching an Existing File or Directory by its read- or write-cap`_
19 6. `Adding Multiple Files or Directories to a Parent Directory at Once`_
20 7. `Unlinking a File or Directory`_
22 6. `Browser Operations: Human-Oriented Interfaces`_
24 1. `Viewing A Directory (as HTML)`_
25 2. `Viewing/Downloading a File`_
26 3. `Getting Information About A File Or Directory (as HTML)`_
27 4. `Creating a Directory`_
28 5. `Uploading a File`_
29 6. `Attaching An Existing File Or Directory (by URI)`_
30 7. `Unlinking A Child`_
31 8. `Renaming A Child`_
33 10. `Debugging and Testing Features`_
35 7. `Other Useful Pages`_
36 8. `Static Files in /public_html`_
37 9. `Safety and Security Issues -- Names vs. URIs`_
38 10. `Concurrency Issues`_
39 11. `Access Blacklist`_
42 Enabling the web-API port
43 =========================
45 Every Tahoe node is capable of running a built-in HTTP server. To enable
46 this, just write a port number into the "[node]web.port" line of your node's
47 tahoe.cfg file. For example, writing "web.port = 3456" into the "[node]"
48 section of $NODEDIR/tahoe.cfg will cause the node to run a webserver on port
51 This string is actually a Twisted "strports" specification, meaning you can
52 get more control over the interface to which the server binds by supplying
53 additional arguments. For more details, see the documentation on
54 `twisted.application.strports
55 <https://twistedmatrix.com/documents/current/api/twisted.application.strports.html>`_.
57 Writing "tcp:3456:interface=127.0.0.1" into the web.port line does the same
58 but binds to the loopback interface, ensuring that only the programs on the
59 local host can connect. Using "ssl:3456:privateKey=mykey.pem:certKey=cert.pem"
62 This webport can be set when the node is created by passing a --webport
63 option to the 'tahoe create-node' command. By default, the node listens on
64 port 3456, on the loopback (127.0.0.1) interface.
67 Basic Concepts: GET, PUT, DELETE, POST
68 ======================================
70 As described in `docs/architecture.rst <../architecture.rst>`_, each file
71 and directory in a Tahoe virtual filesystem is referenced by an identifier
72 that combines the designation of the object with the authority to do something
73 with it (such as read or modify the contents). This identifier is called a
74 "read-cap" or "write-cap", depending upon whether it enables read-only or
75 read-write access. These "caps" are also referred to as URIs (which may be
76 confusing because they are not currently `RFC3986
77 <https://tools.ietf.org/html/rfc3986>`_-compliant URIs).
79 The Tahoe web-based API is "REST-ful", meaning it implements the concepts of
80 "REpresentational State Transfer": the original scheme by which the World
81 Wide Web was intended to work. Each object (file or directory) is referenced
82 by a URL that includes the read- or write- cap. HTTP methods (GET, PUT, and
83 DELETE) are used to manipulate these objects. You can think of the URL as a
84 noun, and the method as a verb.
86 In REST, the GET method is used to retrieve information about an object, or
87 to retrieve some representation of the object itself. When the object is a
88 file, the basic GET method will simply return the contents of that file.
89 Other variations (generally implemented by adding query parameters to the
90 URL) will return information about the object, such as metadata. GET
91 operations are required to have no side-effects.
93 PUT is used to upload new objects into the filesystem, or to replace an
94 existing link or the contents of a mutable file. DELETE is used to unlink
95 objects from directories. Both PUT and DELETE are required to be idempotent:
96 performing the same operation multiple times must have the same side-effects
97 as only performing it once.
99 POST is used for more complicated actions that cannot be expressed as a GET,
100 PUT, or DELETE. POST operations can be thought of as a method call: sending
101 some message to the object referenced by the URL. In Tahoe, POST is also used
102 for operations that must be triggered by an HTML form (including upload and
103 unlinking), because otherwise a regular web browser has no way to accomplish
104 these tasks. In general, everything that can be done with a PUT or DELETE can
105 also be done with a POST.
107 Tahoe's web API is designed for two different kinds of consumer. The first is
108 a program that needs to manipulate the virtual file system. Such programs are
109 expected to use the RESTful interface described above. The second is a human
110 using a standard web browser to work with the filesystem. This user is given
111 a series of HTML pages with links to download files, and forms that use POST
112 actions to upload, rename, and unlink files.
114 When an error occurs, the HTTP response code will be set to an appropriate
115 400-series code (like 404 Not Found for an unknown childname, or 400 Bad Request
116 when the parameters to a web-API operation are invalid), and the HTTP response
117 body will usually contain a few lines of explanation as to the cause of the
118 error and possible responses. Unusual exceptions may result in a 500 Internal
119 Server Error as a catch-all, with a default response body containing
120 a Nevow-generated HTML-ized representation of the Python exception stack trace
121 that caused the problem. CLI programs which want to copy the response body to
122 stderr should provide an "Accept: text/plain" header to their requests to get
123 a plain text stack trace instead. If the Accept header contains ``*/*``, or
124 ``text/*``, or text/html (or if there is no Accept header), HTML tracebacks will
131 Tahoe uses a variety of read- and write- caps to identify files and
132 directories. The most common of these is the "immutable file read-cap", which
133 is used for most uploaded files. These read-caps look like the following::
135 URI:CHK:ime6pvkaxuetdfah2p2f35pe54:4btz54xk3tew6nd4y2ojpxj4m6wxjqqlwnztgre6gnjgtucd5r4a:3:10:202
137 The next most common is a "directory write-cap", which provides both read and
138 write access to a directory, and look like this::
140 URI:DIR2:djrdkfawoqihigoett4g6auz6a:jx5mplfpwexnoqff7y5e4zjus4lidm76dcuarpct7cckorh2dpgq
142 There are also "directory read-caps", which start with "URI:DIR2-RO:", and
143 give read-only access to a directory. Finally there are also mutable file
144 read- and write- caps, which start with "URI:SSK", and give access to mutable
147 (Later versions of Tahoe will make these strings shorter, and will remove the
148 unfortunate colons, which must be escaped when these caps are embedded in
151 To refer to any Tahoe object through the web API, you simply need to combine
152 a prefix (which indicates the HTTP server to use) with the cap (which
153 indicates which object inside that server to access). Since the default Tahoe
154 webport is 3456, the most common prefix is one that will use a local node
155 listening on this port::
157 http://127.0.0.1:3456/uri/ + $CAP
159 So, to access the directory named above (which happens to be the
160 publically-writeable sample directory on the Tahoe test grid, described at
161 http://allmydata.org/trac/tahoe-lafs/wiki/TestGrid), the URL would be::
163 http://127.0.0.1:3456/uri/URI%3ADIR2%3Adjrdkfawoqihigoett4g6auz6a%3Ajx5mplfpwexnoqff7y5e4zjus4lidm76dcuarpct7cckorh2dpgq/
165 (note that the colons in the directory-cap are url-encoded into "%3A"
168 Likewise, to access the file named above, use::
170 http://127.0.0.1:3456/uri/URI%3ACHK%3Aime6pvkaxuetdfah2p2f35pe54%3A4btz54xk3tew6nd4y2ojpxj4m6wxjqqlwnztgre6gnjgtucd5r4a%3A3%3A10%3A202
172 In the rest of this document, we'll use "$DIRCAP" as shorthand for a read-cap
173 or write-cap that refers to a directory, and "$FILECAP" to abbreviate a cap
174 that refers to a file (whether mutable or immutable). So those URLs above can
177 http://127.0.0.1:3456/uri/$DIRCAP/
178 http://127.0.0.1:3456/uri/$FILECAP
180 The operation summaries below will abbreviate these further, by eliding the
181 server prefix. They will be displayed like this::
186 /cap can be used as a synonym for /uri. If interoperability with older web-API
187 servers is required, /uri should be used.
192 Tahoe directories contain named child entries, just like directories in a regular
193 local filesystem. These child entries, called "dirnodes", consist of a name,
194 metadata, a write slot, and a read slot. The write and read slots normally contain
195 a write-cap and read-cap referring to the same object, which can be either a file
196 or a subdirectory. The write slot may be empty (actually, both may be empty,
197 but that is unusual).
199 If you have a Tahoe URL that refers to a directory, and want to reference a
200 named child inside it, just append the child name to the URL. For example, if
201 our sample directory contains a file named "welcome.txt", we can refer to
204 http://127.0.0.1:3456/uri/$DIRCAP/welcome.txt
206 (or http://127.0.0.1:3456/uri/URI%3ADIR2%3Adjrdkfawoqihigoett4g6auz6a%3Ajx5mplfpwexnoqff7y5e4zjus4lidm76dcuarpct7cckorh2dpgq/welcome.txt)
208 Multiple levels of subdirectories can be handled this way::
210 http://127.0.0.1:3456/uri/$DIRCAP/tahoe-source/docs/architecture.rst
212 In this document, when we need to refer to a URL that references a file using
213 this child-of-some-directory format, we'll use the following string::
215 /uri/$DIRCAP/[SUBDIRS../]FILENAME
217 The "[SUBDIRS../]" part means that there are zero or more (optional)
218 subdirectory names in the middle of the URL. The "FILENAME" at the end means
219 that this whole URL refers to a file of some sort, rather than to a
222 When we need to refer specifically to a directory in this way, we'll write::
224 /uri/$DIRCAP/[SUBDIRS../]SUBDIR
227 Note that all components of pathnames in URLs are required to be UTF-8
228 encoded, so "resume.doc" (with an acute accent on both E's) would be accessed
231 http://127.0.0.1:3456/uri/$DIRCAP/r%C3%A9sum%C3%A9.doc
233 Also note that the filenames inside upload POST forms are interpreted using
234 whatever character set was provided in the conventional '_charset' field, and
235 defaults to UTF-8 if not otherwise specified. The JSON representation of each
236 directory contains native Unicode strings. Tahoe directories are specified to
237 contain Unicode filenames, and cannot contain binary strings that are not
238 representable as such.
240 All Tahoe operations that refer to existing files or directories must include
241 a suitable read- or write- cap in the URL: the web-API server won't add one
242 for you. If you don't know the cap, you can't access the file. This allows
243 the security properties of Tahoe caps to be extended across the web-API
247 Slow Operations, Progress, and Cancelling
248 =========================================
250 Certain operations can be expected to take a long time. The "t=deep-check",
251 described below, will recursively visit every file and directory reachable
252 from a given starting point, which can take minutes or even hours for
253 extremely large directory structures. A single long-running HTTP request is a
254 fragile thing: proxies, NAT boxes, browsers, and users may all grow impatient
255 with waiting and give up on the connection.
257 For this reason, long-running operations have an "operation handle", which
258 can be used to poll for status/progress messages while the operation
259 proceeds. This handle can also be used to cancel the operation. These handles
260 are created by the client, and passed in as a an "ophandle=" query argument
261 to the POST or PUT request which starts the operation. The following
262 operations can then be used to retrieve status:
264 ``GET /operations/$HANDLE?output=HTML (with or without t=status)``
266 ``GET /operations/$HANDLE?output=JSON (same)``
268 These two retrieve the current status of the given operation. Each operation
269 presents a different sort of information, but in general the page retrieved
272 * whether the operation is complete, or if it is still running
273 * how much of the operation is complete, and how much is left, if possible
275 Note that the final status output can be quite large: a deep-manifest of a
276 directory structure with 300k directories and 200k unique files is about
277 275MB of JSON, and might take two minutes to generate. For this reason, the
278 full status is not provided until the operation has completed.
280 The HTML form will include a meta-refresh tag, which will cause a regular
281 web browser to reload the status page about 60 seconds later. This tag will
282 be removed once the operation has completed.
284 There may be more status information available under
285 /operations/$HANDLE/$ETC : i.e., the handle forms the root of a URL space.
287 ``POST /operations/$HANDLE?t=cancel``
289 This terminates the operation, and returns an HTML page explaining what was
290 cancelled. If the operation handle has already expired (see below), this
291 POST will return a 404, which indicates that the operation is no longer
292 running (either it was completed or terminated). The response body will be
293 the same as a GET /operations/$HANDLE on this operation handle, and the
294 handle will be expired immediately afterwards.
296 The operation handle will eventually expire, to avoid consuming an unbounded
297 amount of memory. The handle's time-to-live can be reset at any time, by
298 passing a retain-for= argument (with a count of seconds) to either the
299 initial POST that starts the operation, or the subsequent GET request which
300 asks about the operation. For example, if a 'GET
301 /operations/$HANDLE?output=JSON&retain-for=600' query is performed, the
302 handle will remain active for 600 seconds (10 minutes) after the GET was
305 In addition, if the GET includes a release-after-complete=True argument, and
306 the operation has completed, the operation handle will be released
309 If a retain-for= argument is not used, the default handle lifetimes are:
311 * handles will remain valid at least until their operation finishes
312 * uncollected handles for finished operations (i.e. handles for
313 operations that have finished but for which the GET page has not been
314 accessed since completion) will remain valid for four days, or for
315 the total time consumed by the operation, whichever is greater.
316 * collected handles (i.e. the GET page has been retrieved at least once
317 since the operation completed) will remain valid for one day.
319 Many "slow" operations can begin to use unacceptable amounts of memory when
320 operating on large directory structures. The memory usage increases when the
321 ophandle is polled, as the results must be copied into a JSON string, sent
322 over the wire, then parsed by a client. So, as an alternative, many "slow"
323 operations have streaming equivalents. These equivalents do not use operation
324 handles. Instead, they emit line-oriented status results immediately. Client
325 code can cancel the operation by simply closing the HTTP connection.
328 Programmatic Operations
329 =======================
331 Now that we know how to build URLs that refer to files and directories in a
332 Tahoe virtual filesystem, what sorts of operations can we do with those URLs?
333 This section contains a catalog of GET, PUT, DELETE, and POST operations that
334 can be performed on these URLs. This set of operations are aimed at programs
335 that use HTTP to communicate with a Tahoe node. A later section describes
336 operations that are intended for web browsers.
342 ``GET /uri/$FILECAP``
344 ``GET /uri/$DIRCAP/[SUBDIRS../]FILENAME``
346 This will retrieve the contents of the given file. The HTTP response body
347 will contain the sequence of bytes that make up the file.
349 To view files in a web browser, you may want more control over the
350 Content-Type and Content-Disposition headers. Please see the next section
351 "Browser Operations", for details on how to modify these URLs for that
355 Writing/Uploading A File
356 ------------------------
358 ``PUT /uri/$FILECAP``
360 ``PUT /uri/$DIRCAP/[SUBDIRS../]FILENAME``
362 Upload a file, using the data from the HTTP request body, and add whatever
363 child links and subdirectories are necessary to make the file available at
364 the given location. Once this operation succeeds, a GET on the same URL will
365 retrieve the same contents that were just uploaded. This will create any
366 necessary intermediate subdirectories.
368 To use the /uri/$FILECAP form, $FILECAP must be a write-cap for a mutable file.
370 In the /uri/$DIRCAP/[SUBDIRS../]FILENAME form, if the target file is a
371 writeable mutable file, that file's contents will be overwritten
372 in-place. If it is a read-cap for a mutable file, an error will occur.
373 If it is an immutable file, the old file will be discarded, and a new
374 one will be put in its place. If the target file is a writable mutable
375 file, you may also specify an "offset" parameter -- a byte offset that
376 determines where in the mutable file the data from the HTTP request
377 body is placed. This operation is relatively efficient for MDMF mutable
378 files, and is relatively inefficient (but still supported) for SDMF
379 mutable files. If no offset parameter is specified, then the entire
380 file is replaced with the data from the HTTP request body. For an
381 immutable file, the "offset" parameter is not valid.
383 When creating a new file, you can control the type of file created by
384 specifying a format= argument in the query string. format=MDMF creates an
385 MDMF mutable file. format=SDMF creates an SDMF mutable file. format=CHK
386 creates an immutable file. The value of the format argument is
387 case-insensitive. If no format is specified, the newly-created file will be
388 immutable (but see below).
390 For compatibility with previous versions of Tahoe-LAFS, the web-API will
391 also accept a mutable=true argument in the query string. If mutable=true is
392 given, then the new file will be mutable, and its format will be the default
393 mutable file format, as configured by the [client]mutable.format option of
394 tahoe.cfg on the Tahoe-LAFS node hosting the webapi server. Use of
395 mutable=true is discouraged; new code should use format= instead of
396 mutable=true (unless it needs to be compatible with web-API servers older
397 than v1.9.0). If neither format= nor mutable=true are given, the
398 newly-created file will be immutable.
400 This returns the file-cap of the resulting file. If a new file was created
401 by this method, the HTTP response code (as dictated by rfc2616) will be set
402 to 201 CREATED. If an existing file was replaced or modified, the response
405 Note that the 'curl -T localfile http://127.0.0.1:3456/uri/$DIRCAP/foo.txt'
406 command can be used to invoke this operation.
410 This uploads a file, and produces a file-cap for the contents, but does not
411 attach the file into the filesystem. No directories will be modified by
412 this operation. The file-cap is returned as the body of the HTTP response.
414 This method accepts format= and mutable=true as query string arguments, and
415 interprets those arguments in the same way as the linked forms of PUT
416 described immediately above.
418 Creating A New Directory
419 ------------------------
421 ``POST /uri?t=mkdir``
425 Create a new empty directory and return its write-cap as the HTTP response
426 body. This does not make the newly created directory visible from the
427 filesystem. The "PUT" operation is provided for backwards compatibility:
428 new code should use POST.
430 This supports a format= argument in the query string. The format=
431 argument, if specified, controls the format of the directory. format=MDMF
432 indicates that the directory should be stored as an MDMF file; format=SDMF
433 indicates that the directory should be stored as an SDMF file. The value of
434 the format= argument is case-insensitive. If no format= argument is
435 given, the directory's format is determined by the default mutable file
436 format, as configured on the Tahoe-LAFS node responding to the request.
438 ``POST /uri?t=mkdir-with-children``
440 Create a new directory, populated with a set of child nodes, and return its
441 write-cap as the HTTP response body. The new directory is not attached to
442 any other directory: the returned write-cap is the only reference to it.
444 The format of the directory can be controlled with the format= argument in
445 the query string, as described above.
447 Initial children are provided as the body of the POST form (this is more
448 efficient than doing separate mkdir and set_children operations). If the
449 body is empty, the new directory will be empty. If not empty, the body will
450 be interpreted as a UTF-8 JSON-encoded dictionary of children with which the
451 new directory should be populated, using the same format as would be
452 returned in the 'children' value of the t=json GET request, described below.
453 Each dictionary key should be a child name, and each value should be a list
454 of [TYPE, PROPDICT], where PROPDICT contains "rw_uri", "ro_uri", and
455 "metadata" keys (all others are ignored). For example, the PUT request body
459 "Fran\u00e7ais": [ "filenode", {
460 "ro_uri": "URI:CHK:...",
463 "ctime": 1202777696.7564139,
464 "mtime": 1202777696.7564139,
466 "linkcrtime": 1202777696.7564139,
467 "linkmotime": 1202777696.7564139
469 "subdir": [ "dirnode", {
470 "rw_uri": "URI:DIR2:...",
471 "ro_uri": "URI:DIR2-RO:...",
473 "ctime": 1202778102.7589991,
474 "mtime": 1202778111.2160511,
476 "linkcrtime": 1202777696.7564139,
477 "linkmotime": 1202777696.7564139
481 For forward-compatibility, a mutable directory can also contain caps in
482 a format that is unknown to the web-API server. When such caps are retrieved
483 from a mutable directory in a "ro_uri" field, they will be prefixed with
484 the string "ro.", indicating that they must not be decoded without
485 checking that they are read-only. The "ro." prefix must not be stripped
486 off without performing this check. (Future versions of the web-API server
487 will perform it where necessary.)
489 If both the "rw_uri" and "ro_uri" fields are present in a given PROPDICT,
490 and the web-API server recognizes the rw_uri as a write cap, then it will
491 reset the ro_uri to the corresponding read cap and discard the original
492 contents of ro_uri (in order to ensure that the two caps correspond to the
493 same object and that the ro_uri is in fact read-only). However this may not
494 happen for caps in a format unknown to the web-API server. Therefore, when
495 writing a directory the web-API client should ensure that the contents
496 of "rw_uri" and "ro_uri" for a given PROPDICT are a consistent
497 (write cap, read cap) pair if possible. If the web-API client only has
498 one cap and does not know whether it is a write cap or read cap, then
499 it is acceptable to set "rw_uri" to that cap and omit "ro_uri". The
500 client must not put a write cap into a "ro_uri" field.
502 The metadata may have a "no-write" field. If this is set to true in the
503 metadata of a link, it will not be possible to open that link for writing
504 via the SFTP frontend; see `<FTP-and-SFTP.rst>`_ for details.
505 Also, if the "no-write" field is set to true in the metadata of a link to
506 a mutable child, it will cause the link to be diminished to read-only.
508 Note that the web-API-using client application must not provide the
509 "Content-Type: multipart/form-data" header that usually accompanies HTML
510 form submissions, since the body is not formatted this way. Doing so will
511 cause a server error as the lower-level code misparses the request body.
513 Child file names should each be expressed as a Unicode string, then used as
514 keys of the dictionary. The dictionary should then be converted into JSON,
515 and the resulting string encoded into UTF-8. This UTF-8 bytestring should
516 then be used as the POST body.
518 ``POST /uri?t=mkdir-immutable``
520 Like t=mkdir-with-children above, but the new directory will be
521 deep-immutable. This means that the directory itself is immutable, and that
522 it can only contain objects that are treated as being deep-immutable, like
523 immutable files, literal files, and deep-immutable directories.
525 For forward-compatibility, a deep-immutable directory can also contain caps
526 in a format that is unknown to the web-API server. When such caps are retrieved
527 from a deep-immutable directory in a "ro_uri" field, they will be prefixed
528 with the string "imm.", indicating that they must not be decoded without
529 checking that they are immutable. The "imm." prefix must not be stripped
530 off without performing this check. (Future versions of the web-API server
531 will perform it where necessary.)
533 The cap for each child may be given either in the "rw_uri" or "ro_uri"
534 field of the PROPDICT (not both). If a cap is given in the "rw_uri" field,
535 then the web-API server will check that it is an immutable read-cap of a
536 *known* format, and give an error if it is not. If a cap is given in the
537 "ro_uri" field, then the web-API server will still check whether known
538 caps are immutable, but for unknown caps it will simply assume that the
539 cap can be stored, as described above. Note that an attacker would be
540 able to store any cap in an immutable directory, so this check when
541 creating the directory is only to help non-malicious clients to avoid
542 accidentally giving away more authority than intended.
544 A non-empty request body is mandatory, since after the directory is created,
545 it will not be possible to add more children to it.
547 ``POST /uri/$DIRCAP/[SUBDIRS../]SUBDIR?t=mkdir``
549 ``PUT /uri/$DIRCAP/[SUBDIRS../]SUBDIR?t=mkdir``
551 Create new directories as necessary to make sure that the named target
552 ($DIRCAP/SUBDIRS../SUBDIR) is a directory. This will create additional
553 intermediate mutable directories as necessary. If the named target directory
554 already exists, this will make no changes to it.
556 If the final directory is created, it will be empty.
558 This accepts a format= argument in the query string, which controls the
559 format of the named target directory, if it does not already exist. format=
560 is interpreted in the same way as in the POST /uri?t=mkdir form. Note that
561 format= only controls the format of the named target directory;
562 intermediate directories, if created, are created based on the default
563 mutable type, as configured on the Tahoe-LAFS server responding to the
566 This operation will return an error if a blocking file is present at any of
567 the parent names, preventing the server from creating the necessary parent
568 directory; or if it would require changing an immutable directory.
570 The write-cap of the new directory will be returned as the HTTP response
573 ``POST /uri/$DIRCAP/[SUBDIRS../]SUBDIR?t=mkdir-with-children``
575 Like /uri?t=mkdir-with-children, but the final directory is created as a
576 child of an existing mutable directory. This will create additional
577 intermediate mutable directories as necessary. If the final directory is
578 created, it will be populated with initial children from the POST request
579 body, as described above.
581 This accepts a format= argument in the query string, which controls the
582 format of the target directory, if the target directory is created as part
583 of the operation. format= is interpreted in the same way as in the POST/
584 uri?t=mkdir-with-children operation. Note that format= only controls the
585 format of the named target directory; intermediate directories, if created,
586 are created using the default mutable type setting, as configured on the
587 Tahoe-LAFS server responding to the request.
589 This operation will return an error if a blocking file is present at any of
590 the parent names, preventing the server from creating the necessary parent
591 directory; or if it would require changing an immutable directory; or if
592 the immediate parent directory already has a a child named SUBDIR.
594 ``POST /uri/$DIRCAP/[SUBDIRS../]SUBDIR?t=mkdir-immutable``
596 Like /uri?t=mkdir-immutable, but the final directory is created as a child
597 of an existing mutable directory. The final directory will be deep-immutable,
598 and will be populated with the children specified as a JSON dictionary in
599 the POST request body.
601 In Tahoe 1.6 this operation creates intermediate mutable directories if
602 necessary, but that behaviour should not be relied on; see ticket #920.
604 This operation will return an error if the parent directory is immutable,
605 or already has a child named SUBDIR.
607 ``POST /uri/$DIRCAP/[SUBDIRS../]?t=mkdir&name=NAME``
609 Create a new empty mutable directory and attach it to the given existing
610 directory. This will create additional intermediate directories as necessary.
612 This accepts a format= argument in the query string, which controls the
613 format of the named target directory, if it does not already exist. format=
614 is interpreted in the same way as in the POST /uri?t=mkdir form. Note that
615 format= only controls the format of the named target directory;
616 intermediate directories, if created, are created based on the default
617 mutable type, as configured on the Tahoe-LAFS server responding to the
620 This operation will return an error if a blocking file is present at any of
621 the parent names, preventing the server from creating the necessary parent
622 directory, or if it would require changing any immutable directory.
624 The URL of this operation points to the parent of the bottommost new directory,
625 whereas the /uri/$DIRCAP/[SUBDIRS../]SUBDIR?t=mkdir operation above has a URL
626 that points directly to the bottommost new directory.
628 ``POST /uri/$DIRCAP/[SUBDIRS../]?t=mkdir-with-children&name=NAME``
630 Like /uri/$DIRCAP/[SUBDIRS../]?t=mkdir&name=NAME, but the new directory will
631 be populated with initial children via the POST request body. This command
632 will create additional intermediate mutable directories as necessary.
634 This accepts a format= argument in the query string, which controls the
635 format of the target directory, if the target directory is created as part
636 of the operation. format= is interpreted in the same way as in the POST/
637 uri?t=mkdir-with-children operation. Note that format= only controls the
638 format of the named target directory; intermediate directories, if created,
639 are created using the default mutable type setting, as configured on the
640 Tahoe-LAFS server responding to the request.
642 This operation will return an error if a blocking file is present at any of
643 the parent names, preventing the server from creating the necessary parent
644 directory; or if it would require changing an immutable directory; or if
645 the immediate parent directory already has a a child named NAME.
647 Note that the name= argument must be passed as a queryarg, because the POST
648 request body is used for the initial children JSON.
650 ``POST /uri/$DIRCAP/[SUBDIRS../]?t=mkdir-immutable&name=NAME``
652 Like /uri/$DIRCAP/[SUBDIRS../]?t=mkdir-with-children&name=NAME, but the
653 final directory will be deep-immutable. The children are specified as a
654 JSON dictionary in the POST request body. Again, the name= argument must be
655 passed as a queryarg.
657 In Tahoe 1.6 this operation creates intermediate mutable directories if
658 necessary, but that behaviour should not be relied on; see ticket #920.
660 This operation will return an error if the parent directory is immutable,
661 or already has a child named NAME.
664 Getting Information About A File Or Directory (as JSON)
665 -------------------------------------------------------
667 ``GET /uri/$FILECAP?t=json``
669 ``GET /uri/$DIRCAP?t=json``
671 ``GET /uri/$DIRCAP/[SUBDIRS../]SUBDIR?t=json``
673 ``GET /uri/$DIRCAP/[SUBDIRS../]FILENAME?t=json``
675 This returns a machine-parseable JSON-encoded description of the given
676 object. The JSON always contains a list, and the first element of the list is
677 always a flag that indicates whether the referenced object is a file or a
678 directory. If it is a capability to a file, then the information includes
679 file size and URI, like this::
681 GET /uri/$FILECAP?t=json :
685 "verify_uri": verify_uri,
691 If it is a capability to a directory followed by a path from that directory
692 to a file, then the information also includes metadata from the link to the
693 file in the parent directory, like this::
695 GET /uri/$DIRCAP/[SUBDIRS../]FILENAME?t=json
699 "verify_uri": verify_uri,
704 "ctime": 1202777696.7564139,
705 "mtime": 1202777696.7564139,
707 "linkcrtime": 1202777696.7564139,
708 "linkmotime": 1202777696.7564139
711 If it is a directory, then it includes information about the children of
712 this directory, as a mapping from child name to a set of data about the
713 child (the same data that would appear in a corresponding GET?t=json of the
714 child itself). The child entries also include metadata about each child,
715 including link-creation- and link-change- timestamps. The output looks like
718 GET /uri/$DIRCAP?t=json :
719 GET /uri/$DIRCAP/[SUBDIRS../]SUBDIR?t=json :
722 "rw_uri": read_write_uri,
723 "ro_uri": read_only_uri,
724 "verify_uri": verify_uri,
728 "foo.txt": [ "filenode",
733 "ctime": 1202777696.7564139,
734 "mtime": 1202777696.7564139,
736 "linkcrtime": 1202777696.7564139,
737 "linkmotime": 1202777696.7564139
739 "subdir": [ "dirnode",
744 "ctime": 1202778102.7589991,
745 "mtime": 1202778111.2160511,
747 "linkcrtime": 1202777696.7564139,
748 "linkmotime": 1202777696.7564139
752 In the above example, note how 'children' is a dictionary in which the keys
753 are child names and the values depend upon whether the child is a file or a
754 directory. The value is mostly the same as the JSON representation of the
755 child object (except that directories do not recurse -- the "children"
756 entry of the child is omitted, and the directory view includes the metadata
757 that is stored on the directory edge).
759 The rw_uri field will be present in the information about a directory
760 if and only if you have read-write access to that directory. The verify_uri
761 field will be present if and only if the object has a verify-cap
762 (non-distributed LIT files do not have verify-caps).
764 If the cap is of an unknown format, then the file size and verify_uri will
767 GET /uri/$UNKNOWNCAP?t=json :
770 "ro_uri": unknown_read_uri
773 GET /uri/$DIRCAP/[SUBDIRS../]UNKNOWNCHILDNAME?t=json :
776 "rw_uri": unknown_write_uri,
777 "ro_uri": unknown_read_uri,
780 "ctime": 1202777696.7564139,
781 "mtime": 1202777696.7564139,
783 "linkcrtime": 1202777696.7564139,
784 "linkmotime": 1202777696.7564139
787 As in the case of file nodes, the metadata will only be present when the
788 capability is to a directory followed by a path. The "mutable" field is also
789 not always present; when it is absent, the mutability of the object is not
795 The value of the 'tahoe':'linkmotime' key is updated whenever a link to a
796 child is set. The value of the 'tahoe':'linkcrtime' key is updated whenever
797 a link to a child is created -- i.e. when there was not previously a link
800 Note however, that if the edge in the Tahoe filesystem points to a mutable
801 file and the contents of that mutable file is changed, then the
802 'tahoe':'linkmotime' value on that edge will *not* be updated, since the
803 edge itself wasn't updated -- only the mutable file was.
805 The timestamps are represented as a number of seconds since the UNIX epoch
806 (1970-01-01 00:00:00 UTC), with leap seconds not being counted in the long
809 In Tahoe earlier than v1.4.0, 'mtime' and 'ctime' keys were populated
810 instead of the 'tahoe':'linkmotime' and 'tahoe':'linkcrtime' keys. Starting
811 in Tahoe v1.4.0, the 'linkmotime'/'linkcrtime' keys in the 'tahoe' sub-dict
812 are populated. However, prior to Tahoe v1.7beta, a bug caused the 'tahoe'
813 sub-dict to be deleted by web-API requests in which new metadata is
814 specified, and not to be added to existing child links that lack it.
816 From Tahoe v1.7.0 onward, the 'mtime' and 'ctime' fields are no longer
817 populated or updated (see ticket #924), except by "tahoe backup" as
818 explained below. For backward compatibility, when an existing link is
819 updated and 'tahoe':'linkcrtime' is not present in the previous metadata
820 but 'ctime' is, the old value of 'ctime' is used as the new value of
821 'tahoe':'linkcrtime'.
823 The reason we added the new fields in Tahoe v1.4.0 is that there is a
824 "set_children" API (described below) which you can use to overwrite the
825 values of the 'mtime'/'ctime' pair, and this API is used by the
826 "tahoe backup" command (in Tahoe v1.3.0 and later) to set the 'mtime' and
827 'ctime' values when backing up files from a local filesystem into the
828 Tahoe filesystem. As of Tahoe v1.4.0, the set_children API cannot be used
829 to set anything under the 'tahoe' key of the metadata dict -- if you
830 include 'tahoe' keys in your 'metadata' arguments then it will silently
833 Therefore, if the 'tahoe' sub-dict is present, you can rely on the
834 'linkcrtime' and 'linkmotime' values therein to have the semantics described
835 above. (This is assuming that only official Tahoe clients have been used to
836 write those links, and that their system clocks were set to what you expected
837 -- there is nothing preventing someone from editing their Tahoe client or
838 writing their own Tahoe client which would overwrite those values however
839 they like, and there is nothing to constrain their system clock from taking
842 When an edge is created or updated by "tahoe backup", the 'mtime' and
843 'ctime' keys on that edge are set as follows:
845 * 'mtime' is set to the timestamp read from the local filesystem for the
846 "mtime" of the local file in question, which means the last time the
847 contents of that file were changed.
849 * On Windows, 'ctime' is set to the creation timestamp for the file
850 read from the local filesystem. On other platforms, 'ctime' is set to
851 the UNIX "ctime" of the local file, which means the last time that
852 either the contents or the metadata of the local file was changed.
854 There are several ways that the 'ctime' field could be confusing:
856 1. You might be confused about whether it reflects the time of the creation
857 of a link in the Tahoe filesystem (by a version of Tahoe < v1.7.0) or a
858 timestamp copied in by "tahoe backup" from a local filesystem.
860 2. You might be confused about whether it is a copy of the file creation
861 time (if "tahoe backup" was run on a Windows system) or of the last
862 contents-or-metadata change (if "tahoe backup" was run on a different
865 3. You might be confused by the fact that changing the contents of a
866 mutable file in Tahoe doesn't have any effect on any links pointing at
867 that file in any directories, although "tahoe backup" sets the link
868 'ctime'/'mtime' to reflect timestamps about the local file corresponding
869 to the Tahoe file to which the link points.
871 4. Also, quite apart from Tahoe, you might be confused about the meaning
872 of the "ctime" in UNIX local filesystems, which people sometimes think
873 means file creation time, but which actually means, in UNIX local
874 filesystems, the most recent time that the file contents or the file
875 metadata (such as owner, permission bits, extended attributes, etc.)
876 has changed. Note that although "ctime" does not mean file creation time
877 in UNIX, links created by a version of Tahoe prior to v1.7.0, and never
878 written by "tahoe backup", will have 'ctime' set to the link creation
882 Attaching an Existing File or Directory by its read- or write-cap
883 -----------------------------------------------------------------
885 ``PUT /uri/$DIRCAP/[SUBDIRS../]CHILDNAME?t=uri``
887 This attaches a child object (either a file or directory) to a specified
888 location in the virtual filesystem. The child object is referenced by its
889 read- or write- cap, as provided in the HTTP request body. This will create
890 intermediate directories as necessary.
892 This is similar to a UNIX hardlink: by referencing a previously-uploaded file
893 (or previously-created directory) instead of uploading/creating a new one,
894 you can create two references to the same object.
896 The read- or write- cap of the child is provided in the body of the HTTP
897 request, and this same cap is returned in the response body.
899 The default behavior is to overwrite any existing object at the same
900 location. To prevent this (and make the operation return an error instead
901 of overwriting), add a "replace=false" argument, as "?t=uri&replace=false".
902 With replace=false, this operation will return an HTTP 409 "Conflict" error
903 if there is already an object at the given location, rather than
904 overwriting the existing object. To allow the operation to overwrite a
905 file, but return an error when trying to overwrite a directory, use
906 "replace=only-files" (this behavior is closer to the traditional UNIX "mv"
907 command). Note that "true", "t", and "1" are all synonyms for "True", and
908 "false", "f", and "0" are synonyms for "False", and the parameter is
911 Note that this operation does not take its child cap in the form of
912 separate "rw_uri" and "ro_uri" fields. Therefore, it cannot accept a
913 child cap in a format unknown to the web-API server, unless its URI
914 starts with "ro." or "imm.". This restriction is necessary because the
915 server is not able to attenuate an unknown write cap to a read cap.
916 Unknown URIs starting with "ro." or "imm.", on the other hand, are
917 assumed to represent read caps. The client should not prefix a write
918 cap with "ro." or "imm." and pass it to this operation, since that
919 would result in granting the cap's write authority to holders of the
923 Adding Multiple Files or Directories to a Parent Directory at Once
924 ------------------------------------------------------------------
926 ``POST /uri/$DIRCAP/[SUBDIRS..]?t=set_children``
928 ``POST /uri/$DIRCAP/[SUBDIRS..]?t=set-children`` (Tahoe >= v1.6)
930 This command adds multiple children to a directory in a single operation.
931 It reads the request body and interprets it as a JSON-encoded description
932 of the child names and read/write-caps that should be added.
934 The body should be a JSON-encoded dictionary, in the same format as the
935 "children" value returned by the "GET /uri/$DIRCAP?t=json" operation
936 described above. In this format, each key is a child names, and the
937 corresponding value is a tuple of (type, childinfo). "type" is ignored, and
938 "childinfo" is a dictionary that contains "rw_uri", "ro_uri", and
939 "metadata" keys. You can take the output of "GET /uri/$DIRCAP1?t=json" and
940 use it as the input to "POST /uri/$DIRCAP2?t=set_children" to make DIR2
941 look very much like DIR1 (except for any existing children of DIR2 that
942 were not overwritten, and any existing "tahoe" metadata keys as described
945 When the set_children request contains a child name that already exists in
946 the target directory, this command defaults to overwriting that child with
947 the new value (both child cap and metadata, but if the JSON data does not
948 contain a "metadata" key, the old child's metadata is preserved). The
949 command takes a boolean "overwrite=" query argument to control this
950 behavior. If you use "?t=set_children&overwrite=false", then an attempt to
951 replace an existing child will instead cause an error.
953 Any "tahoe" key in the new child's "metadata" value is ignored. Any
954 existing "tahoe" metadata is preserved. The metadata["tahoe"] value is
955 reserved for metadata generated by the tahoe node itself. The only two keys
956 currently placed here are "linkcrtime" and "linkmotime". For details, see
957 the section above entitled "Get Information About A File Or Directory (as
958 JSON)", in the "About the metadata" subsection.
960 Note that this command was introduced with the name "set_children", which
961 uses an underscore rather than a hyphen as other multi-word command names
962 do. The variant with a hyphen is now accepted, but clients that desire
963 backward compatibility should continue to use "set_children".
966 Unlinking a File or Directory
967 -----------------------------
969 ``DELETE /uri/$DIRCAP/[SUBDIRS../]CHILDNAME``
971 This removes the given name from its parent directory. CHILDNAME is the
972 name to be removed, and $DIRCAP/SUBDIRS.. indicates the directory that will
975 Note that this does not actually delete the file or directory that the name
976 points to from the tahoe grid -- it only unlinks the named reference from
977 this directory. If there are other names in this directory or in other
978 directories that point to the resource, then it will remain accessible
979 through those paths. Even if all names pointing to this object are removed
980 from their parent directories, then someone with possession of its read-cap
981 can continue to access the object through that cap.
983 The object will only become completely unreachable once 1: there are no
984 reachable directories that reference it, and 2: nobody is holding a read-
985 or write- cap to the object. (This behavior is very similar to the way
986 hardlinks and anonymous files work in traditional UNIX filesystems).
988 This operation will not modify more than a single directory. Intermediate
989 directories which were implicitly created by PUT or POST methods will *not*
990 be automatically removed by DELETE.
992 This method returns the file- or directory- cap of the object that was just
996 Browser Operations: Human-oriented interfaces
997 =============================================
999 This section describes the HTTP operations that provide support for humans
1000 running a web browser. Most of these operations use HTML forms that use POST
1001 to drive the Tahoe node. This section is intended for HTML authors who want
1002 to write web pages that contain forms and buttons which manipulate the Tahoe
1005 Note that for all POST operations, the arguments listed can be provided
1006 either as URL query arguments or as form body fields. URL query arguments are
1007 separated from the main URL by "?", and from each other by "&". For example,
1008 "POST /uri/$DIRCAP?t=upload&mutable=true". Form body fields are usually
1009 specified by using <input type="hidden"> elements. For clarity, the
1010 descriptions below display the most significant arguments as URL query args.
1013 Viewing A Directory (as HTML)
1014 -----------------------------
1016 ``GET /uri/$DIRCAP/[SUBDIRS../]``
1018 This returns an HTML page, intended to be displayed to a human by a web
1019 browser, which contains HREF links to all files and directories reachable
1020 from this directory. These HREF links do not have a t= argument, meaning
1021 that a human who follows them will get pages also meant for a human. It also
1022 contains forms to upload new files, and to unlink files and directories
1023 from their parent directory. Those forms use POST methods to do their job.
1026 Viewing/Downloading a File
1027 --------------------------
1029 ``GET /uri/$FILECAP``
1031 ``GET /uri/$DIRCAP/[SUBDIRS../]FILENAME``
1033 This will retrieve the contents of the given file. The HTTP response body
1034 will contain the sequence of bytes that make up the file.
1036 If you want the HTTP response to include a useful Content-Type header,
1037 either use the second form (which starts with a $DIRCAP), or add a
1038 "filename=foo" query argument, like "GET /uri/$FILECAP?filename=foo.jpg".
1039 The bare "GET /uri/$FILECAP" does not give the Tahoe node enough information
1040 to determine a Content-Type (since Tahoe immutable files are merely
1041 sequences of bytes, not typed+named file objects).
1043 If the URL has both filename= and "save=true" in the query arguments, then
1044 the server to add a "Content-Disposition: attachment" header, along with a
1045 filename= parameter. When a user clicks on such a link, most browsers will
1046 offer to let the user save the file instead of displaying it inline (indeed,
1047 most browsers will refuse to display it inline). "true", "t", "1", and other
1048 case-insensitive equivalents are all treated the same.
1050 Character-set handling in URLs and HTTP headers is a dubious art [1]_. For
1051 maximum compatibility, Tahoe simply copies the bytes from the filename=
1052 argument into the Content-Disposition header's filename= parameter, without
1053 trying to interpret them in any particular way.
1056 ``GET /named/$FILECAP/FILENAME``
1058 This is an alternate download form which makes it easier to get the correct
1059 filename. The Tahoe server will provide the contents of the given file, with
1060 a Content-Type header derived from the given filename. This form is used to
1061 get browsers to use the "Save Link As" feature correctly, and also helps
1062 command-line tools like "wget" and "curl" use the right filename. Note that
1063 this form can *only* be used with file caps; it is an error to use a
1064 directory cap after the /named/ prefix.
1066 URLs may also use /file/$FILECAP/FILENAME as a synonym for
1067 /named/$FILECAP/FILENAME.
1069 Getting Information About A File Or Directory (as HTML)
1070 -------------------------------------------------------
1072 ``GET /uri/$FILECAP?t=info``
1074 ``GET /uri/$DIRCAP/?t=info``
1076 ``GET /uri/$DIRCAP/[SUBDIRS../]SUBDIR/?t=info``
1078 ``GET /uri/$DIRCAP/[SUBDIRS../]FILENAME?t=info``
1080 This returns a human-oriented HTML page with more detail about the selected
1081 file or directory object. This page contains the following items:
1085 * JSON representation
1086 * raw contents (text/plain)
1087 * access caps (URIs): verify-cap, read-cap, write-cap (for mutable objects)
1088 * check/verify/repair form
1089 * deep-check/deep-size/deep-stats/manifest (for directories)
1090 * replace-contents form (for mutable files)
1093 Creating a Directory
1094 --------------------
1096 ``POST /uri?t=mkdir``
1098 This creates a new empty directory, but does not attach it to the virtual
1101 If a "redirect_to_result=true" argument is provided, then the HTTP response
1102 will cause the web browser to be redirected to a /uri/$DIRCAP page that
1103 gives access to the newly-created directory. If you bookmark this page,
1104 you'll be able to get back to the directory again in the future. This is the
1105 recommended way to start working with a Tahoe server: create a new unlinked
1106 directory (using redirect_to_result=true), then bookmark the resulting
1107 /uri/$DIRCAP page. There is a "create directory" button on the Welcome page
1108 to invoke this action.
1110 This accepts a format= argument in the query string. Refer to the
1111 documentation of the PUT /uri?t=mkdir operation in `Creating A
1112 New Directory`_ for information on the behavior of the format= argument.
1114 If "redirect_to_result=true" is not provided (or is given a value of
1115 "false"), then the HTTP response body will simply be the write-cap of the
1118 ``POST /uri/$DIRCAP/[SUBDIRS../]?t=mkdir&name=CHILDNAME``
1120 This creates a new empty directory as a child of the designated SUBDIR. This
1121 will create additional intermediate directories as necessary.
1123 This accepts a format= argument in the query string. Refer to the
1124 documentation of POST /uri/$DIRCAP/[SUBDIRS../]?t=mkdir&name=CHILDNAME in
1125 `Creating A New Directory`_ for information on the behavior of the format=
1128 If a "when_done=URL" argument is provided, the HTTP response will cause the
1129 web browser to redirect to the given URL. This provides a convenient way to
1130 return the browser to the directory that was just modified. Without a
1131 when_done= argument, the HTTP response will simply contain the write-cap of
1132 the directory that was just created.
1138 ``POST /uri?t=upload``
1140 This uploads a file, and produces a file-cap for the contents, but does not
1141 attach the file into the filesystem. No directories will be modified by
1144 The file must be provided as the "file" field of an HTML encoded form body,
1145 produced in response to an HTML form like this::
1147 <form action="/uri" method="POST" enctype="multipart/form-data">
1148 <input type="hidden" name="t" value="upload" />
1149 <input type="file" name="file" />
1150 <input type="submit" value="Upload Unlinked" />
1153 If a "when_done=URL" argument is provided, the response body will cause the
1154 browser to redirect to the given URL. If the when_done= URL has the string
1155 "%(uri)s" in it, that string will be replaced by a URL-escaped form of the
1156 newly created file-cap. (Note that without this substitution, there is no
1157 way to access the file that was just uploaded).
1159 The default (in the absence of when_done=) is to return an HTML page that
1160 describes the results of the upload. This page will contain information
1161 about which storage servers were used for the upload, how long each
1162 operation took, etc.
1164 This accepts format= and mutable=true query string arguments. Refer to
1165 `Writing/Uploading A File`_ for information on the behavior of format= and
1168 ``POST /uri/$DIRCAP/[SUBDIRS../]?t=upload``
1170 This uploads a file, and attaches it as a new child of the given directory,
1171 which must be mutable. The file must be provided as the "file" field of an
1172 HTML-encoded form body, produced in response to an HTML form like this::
1174 <form action="." method="POST" enctype="multipart/form-data">
1175 <input type="hidden" name="t" value="upload" />
1176 <input type="file" name="file" />
1177 <input type="submit" value="Upload" />
1180 A "name=" argument can be provided to specify the new child's name,
1181 otherwise it will be taken from the "filename" field of the upload form
1182 (most web browsers will copy the last component of the original file's
1183 pathname into this field). To avoid confusion, name= is not allowed to
1186 If there is already a child with that name, and it is a mutable file, then
1187 its contents are replaced with the data being uploaded. If it is not a
1188 mutable file, the default behavior is to remove the existing child before
1189 creating a new one. To prevent this (and make the operation return an error
1190 instead of overwriting the old child), add a "replace=false" argument, as
1191 "?t=upload&replace=false". With replace=false, this operation will return an
1192 HTTP 409 "Conflict" error if there is already an object at the given
1193 location, rather than overwriting the existing object. Note that "true",
1194 "t", and "1" are all synonyms for "True", and "false", "f", and "0" are
1195 synonyms for "False". the parameter is case-insensitive.
1197 This will create additional intermediate directories as necessary, although
1198 since it is expected to be triggered by a form that was retrieved by "GET
1199 /uri/$DIRCAP/[SUBDIRS../]", it is likely that the parent directory will
1202 This accepts format= and mutable=true query string arguments. Refer to
1203 `Writing/Uploading A File`_ for information on the behavior of format= and
1206 If a "when_done=URL" argument is provided, the HTTP response will cause the
1207 web browser to redirect to the given URL. This provides a convenient way to
1208 return the browser to the directory that was just modified. Without a
1209 when_done= argument, the HTTP response will simply contain the file-cap of
1210 the file that was just uploaded (a write-cap for mutable files, or a
1211 read-cap for immutable files).
1213 ``POST /uri/$DIRCAP/[SUBDIRS../]FILENAME?t=upload``
1215 This also uploads a file and attaches it as a new child of the given
1216 directory, which must be mutable. It is a slight variant of the previous
1217 operation, as the URL refers to the target file rather than the parent
1218 directory. It is otherwise identical: this accepts mutable= and when_done=
1221 ``POST /uri/$FILECAP?t=upload``
1223 This modifies the contents of an existing mutable file in-place. An error is
1224 signalled if $FILECAP does not refer to a mutable file. It behaves just like
1225 the "PUT /uri/$FILECAP" form, but uses a POST for the benefit of HTML forms
1229 Attaching An Existing File Or Directory (by URI)
1230 ------------------------------------------------
1232 ``POST /uri/$DIRCAP/[SUBDIRS../]?t=uri&name=CHILDNAME&uri=CHILDCAP``
1234 This attaches a given read- or write- cap "CHILDCAP" to the designated
1235 directory, with a specified child name. This behaves much like the PUT t=uri
1236 operation, and is a lot like a UNIX hardlink. It is subject to the same
1237 restrictions as that operation on the use of cap formats unknown to the
1240 This will create additional intermediate directories as necessary, although
1241 since it is expected to be triggered by a form that was retrieved by "GET
1242 /uri/$DIRCAP/[SUBDIRS../]", it is likely that the parent directory will
1245 This accepts the same replace= argument as POST t=upload.
1251 ``POST /uri/$DIRCAP/[SUBDIRS../]?t=delete&name=CHILDNAME``
1253 ``POST /uri/$DIRCAP/[SUBDIRS../]?t=unlink&name=CHILDNAME``
1255 This instructs the node to remove a child object (file or subdirectory) from
1256 the given directory, which must be mutable. Note that the entire subtree is
1257 unlinked from the parent. Unlike deleting a subdirectory in a UNIX local
1258 filesystem, the subtree need not be empty; if it isn't, then other references
1259 into the subtree will see that the child subdirectories are not modified by
1260 this operation. Only the link from the given directory to its child is severed.
1262 In Tahoe-LAFS v1.9.0 and later, t=unlink can be used as a synonym for t=delete.
1263 If interoperability with older web-API servers is required, t=delete should
1270 ``POST /uri/$DIRCAP/[SUBDIRS../]?t=rename&from_name=OLD&to_name=NEW``
1272 This instructs the node to rename a child of the given directory, which must
1273 be mutable. This has a similar effect to removing the child, then adding the
1274 same child-cap under the new name, except that it preserves metadata. This
1275 operation cannot move the child to a different directory.
1277 This operation will replace any existing child of the new name, making it
1278 behave like the UNIX "``mv -f``" command.
1283 ``GET /uri?uri=$CAP``
1285 This causes a redirect to /uri/$CAP, and retains any additional query
1286 arguments (like filename= or save=). This is for the convenience of web
1287 forms which allow the user to paste in a read- or write- cap (obtained
1288 through some out-of-band channel, like IM or email).
1290 Note that this form merely redirects to the specific file or directory
1291 indicated by the $CAP: unlike the GET /uri/$DIRCAP form, you cannot
1292 traverse to children by appending additional path segments to the URL.
1294 ``GET /uri/$DIRCAP/[SUBDIRS../]?t=rename-form&name=$CHILDNAME``
1296 This provides a useful facility to browser-based user interfaces. It
1297 returns a page containing a form targetting the "POST $DIRCAP t=rename"
1298 functionality described above, with the provided $CHILDNAME present in the
1299 'from_name' field of that form. I.e. this presents a form offering to
1300 rename $CHILDNAME, requesting the new name, and submitting POST rename.
1302 ``GET /uri/$DIRCAP/[SUBDIRS../]CHILDNAME?t=uri``
1304 This returns the file- or directory- cap for the specified object.
1306 ``GET /uri/$DIRCAP/[SUBDIRS../]CHILDNAME?t=readonly-uri``
1308 This returns a read-only file- or directory- cap for the specified object.
1309 If the object is an immutable file, this will return the same value as
1313 Debugging and Testing Features
1314 ------------------------------
1316 These URLs are less-likely to be helpful to the casual Tahoe user, and are
1317 mainly intended for developers.
1319 ``POST $URL?t=check``
1321 This triggers the FileChecker to determine the current "health" of the
1322 given file or directory, by counting how many shares are available. The
1323 page that is returned will display the results. This can be used as a "show
1324 me detailed information about this file" page.
1326 If a verify=true argument is provided, the node will perform a more
1327 intensive check, downloading and verifying every single bit of every share.
1329 If an add-lease=true argument is provided, the node will also add (or
1330 renew) a lease to every share it encounters. Each lease will keep the share
1331 alive for a certain period of time (one month by default). Once the last
1332 lease expires or is explicitly cancelled, the storage server is allowed to
1335 If an output=JSON argument is provided, the response will be
1336 machine-readable JSON instead of human-oriented HTML. The data is a
1337 dictionary with the following keys::
1339 storage-index: a base32-encoded string with the objects's storage index,
1340 or an empty string for LIT files
1341 summary: a string, with a one-line summary of the stats of the file
1342 results: a dictionary that describes the state of the file. For LIT files,
1343 this dictionary has only the 'healthy' key, which will always be
1344 True. For distributed files, this dictionary has the following
1346 count-shares-good: the number of good shares that were found
1347 count-shares-needed: 'k', the number of shares required for recovery
1348 count-shares-expected: 'N', the number of total shares generated
1349 count-good-share-hosts: this was intended to be the number of distinct
1350 storage servers with good shares. It is currently
1351 (as of Tahoe-LAFS v1.8.0) computed incorrectly;
1353 count-wrong-shares: for mutable files, the number of shares for
1354 versions other than the 'best' one (highest
1355 sequence number, highest roothash). These are
1357 count-recoverable-versions: for mutable files, the number of
1358 recoverable versions of the file. For
1359 a healthy file, this will equal 1.
1360 count-unrecoverable-versions: for mutable files, the number of
1361 unrecoverable versions of the file.
1362 For a healthy file, this will be 0.
1363 count-corrupt-shares: the number of shares with integrity failures
1364 list-corrupt-shares: a list of "share locators", one for each share
1365 that was found to be corrupt. Each share locator
1366 is a list of (serverid, storage_index, sharenum).
1367 needs-rebalancing: (bool) True if there are multiple shares on a single
1368 storage server, indicating a reduction in reliability
1369 that could be resolved by moving shares to new
1371 servers-responding: list of base32-encoded storage server identifiers,
1372 one for each server which responded to the share
1374 healthy: (bool) True if the file is completely healthy, False otherwise.
1375 Healthy files have at least N good shares. Overlapping shares
1376 do not currently cause a file to be marked unhealthy. If there
1377 are at least N good shares, then corrupt shares do not cause the
1378 file to be marked unhealthy, although the corrupt shares will be
1379 listed in the results (list-corrupt-shares) and should be manually
1380 removed to wasting time in subsequent downloads (as the
1381 downloader rediscovers the corruption and uses alternate shares).
1382 Future compatibility: the meaning of this field may change to
1383 reflect whether the servers-of-happiness criterion is met
1385 sharemap: dict mapping share identifier to list of serverids
1386 (base32-encoded strings). This indicates which servers are
1387 holding which shares. For immutable files, the shareid is
1388 an integer (the share number, from 0 to N-1). For
1389 immutable files, it is a string of the form
1390 'seq%d-%s-sh%d', containing the sequence number, the
1391 roothash, and the share number.
1393 ``POST $URL?t=start-deep-check`` (must add &ophandle=XYZ)
1395 This initiates a recursive walk of all files and directories reachable from
1396 the target, performing a check on each one just like t=check. The result
1397 page will contain a summary of the results, including details on any
1398 file/directory that was not fully healthy.
1400 t=start-deep-check can only be invoked on a directory. An error (400
1401 BAD_REQUEST) will be signalled if it is invoked on a file. The recursive
1402 walker will deal with loops safely.
1404 This accepts the same verify= and add-lease= arguments as t=check.
1406 Since this operation can take a long time (perhaps a second per object),
1407 the ophandle= argument is required (see "Slow Operations, Progress, and
1408 Cancelling" above). The response to this POST will be a redirect to the
1409 corresponding /operations/$HANDLE page (with output=HTML or output=JSON to
1410 match the output= argument given to the POST). The deep-check operation
1411 will continue to run in the background, and the /operations page should be
1412 used to find out when the operation is done.
1414 Detailed check results for non-healthy files and directories will be
1415 available under /operations/$HANDLE/$STORAGEINDEX, and the HTML status will
1416 contain links to these detailed results.
1418 The HTML /operations/$HANDLE page for incomplete operations will contain a
1419 meta-refresh tag, set to 60 seconds, so that a browser which uses
1420 deep-check will automatically poll until the operation has completed.
1422 The JSON page (/options/$HANDLE?output=JSON) will contain a
1423 machine-readable JSON dictionary with the following keys::
1425 finished: a boolean, True if the operation is complete, else False. Some
1426 of the remaining keys may not be present until the operation
1428 root-storage-index: a base32-encoded string with the storage index of the
1429 starting point of the deep-check operation
1430 count-objects-checked: count of how many objects were checked. Note that
1431 non-distributed objects (i.e. small immutable LIT
1432 files) are not checked, since for these objects,
1433 the data is contained entirely in the URI.
1434 count-objects-healthy: how many of those objects were completely healthy
1435 count-objects-unhealthy: how many were damaged in some way
1436 count-corrupt-shares: how many shares were found to have corruption,
1437 summed over all objects examined
1438 list-corrupt-shares: a list of "share identifiers", one for each share
1439 that was found to be corrupt. Each share identifier
1440 is a list of (serverid, storage_index, sharenum).
1441 list-unhealthy-files: a list of (pathname, check-results) tuples, for
1442 each file that was not fully healthy. 'pathname' is
1443 a list of strings (which can be joined by "/"
1444 characters to turn it into a single string),
1445 relative to the directory on which deep-check was
1446 invoked. The 'check-results' field is the same as
1447 that returned by t=check&output=JSON, described
1449 stats: a dictionary with the same keys as the t=start-deep-stats command
1452 ``POST $URL?t=stream-deep-check``
1454 This initiates a recursive walk of all files and directories reachable from
1455 the target, performing a check on each one just like t=check. For each
1456 unique object (duplicates are skipped), a single line of JSON is emitted to
1457 the HTTP response channel (or an error indication, see below). When the walk
1458 is complete, a final line of JSON is emitted which contains the accumulated
1459 file-size/count "deep-stats" data.
1461 This command takes the same arguments as t=start-deep-check.
1463 A CLI tool can split the response stream on newlines into "response units",
1464 and parse each response unit as JSON. Each such parsed unit will be a
1465 dictionary, and will contain at least the "type" key: a string, one of
1466 "file", "directory", or "stats".
1468 For all units that have a type of "file" or "directory", the dictionary will
1469 contain the following keys::
1471 "path": a list of strings, with the path that is traversed to reach the
1473 "cap": a write-cap URI for the file or directory, if available, else a
1475 "verifycap": a verify-cap URI for the file or directory
1476 "repaircap": an URI for the weakest cap that can still be used to repair
1478 "storage-index": a base32 storage index for the object
1479 "check-results": a copy of the dictionary which would be returned by
1480 t=check&output=json, with three top-level keys:
1481 "storage-index", "summary", and "results", and a variety
1482 of counts and sharemaps in the "results" value.
1484 Note that non-distributed files (i.e. LIT files) will have values of None
1485 for verifycap, repaircap, and storage-index, since these files can neither
1486 be verified nor repaired, and are not stored on the storage servers.
1487 Likewise the check-results dictionary will be limited: an empty string for
1488 storage-index, and a results dictionary with only the "healthy" key.
1490 The last unit in the stream will have a type of "stats", and will contain
1491 the keys described in the "start-deep-stats" operation, below.
1493 If any errors occur during the traversal (specifically if a directory is
1494 unrecoverable, such that further traversal is not possible), an error
1495 indication is written to the response body, instead of the usual line of
1496 JSON. This error indication line will begin with the string "ERROR:" (in all
1497 caps), and contain a summary of the error on the rest of the line. The
1498 remaining lines of the response body will be a python exception. The client
1499 application should look for the ERROR: and stop processing JSON as soon as
1500 it is seen. Note that neither a file being unrecoverable nor a directory
1501 merely being unhealthy will cause traversal to stop. The line just before
1502 the ERROR: will describe the directory that was untraversable, since the
1503 unit is emitted to the HTTP response body before the child is traversed.
1506 ``POST $URL?t=check&repair=true``
1508 This performs a health check of the given file or directory, and if the
1509 checker determines that the object is not healthy (some shares are missing
1510 or corrupted), it will perform a "repair". During repair, any missing
1511 shares will be regenerated and uploaded to new servers.
1513 This accepts the same verify=true and add-lease= arguments as t=check. When
1514 an output=JSON argument is provided, the machine-readable JSON response
1515 will contain the following keys::
1517 storage-index: a base32-encoded string with the objects's storage index,
1518 or an empty string for LIT files
1519 repair-attempted: (bool) True if repair was attempted
1520 repair-successful: (bool) True if repair was attempted and the file was
1521 fully healthy afterwards. False if no repair was
1522 attempted, or if a repair attempt failed.
1523 pre-repair-results: a dictionary that describes the state of the file
1524 before any repair was performed. This contains exactly
1525 the same keys as the 'results' value of the t=check
1526 response, described above.
1527 post-repair-results: a dictionary that describes the state of the file
1528 after any repair was performed. If no repair was
1529 performed, post-repair-results and pre-repair-results
1530 will be the same. This contains exactly the same keys
1531 as the 'results' value of the t=check response,
1534 ``POST $URL?t=start-deep-check&repair=true`` (must add &ophandle=XYZ)
1536 This triggers a recursive walk of all files and directories, performing a
1537 t=check&repair=true on each one.
1539 Like t=start-deep-check without the repair= argument, this can only be
1540 invoked on a directory. An error (400 BAD_REQUEST) will be signalled if it
1541 is invoked on a file. The recursive walker will deal with loops safely.
1543 This accepts the same verify= and add-lease= arguments as
1544 t=start-deep-check. It uses the same ophandle= mechanism as
1545 start-deep-check. When an output=JSON argument is provided, the response
1546 will contain the following keys::
1548 finished: (bool) True if the operation has completed, else False
1549 root-storage-index: a base32-encoded string with the storage index of the
1550 starting point of the deep-check operation
1551 count-objects-checked: count of how many objects were checked
1553 count-objects-healthy-pre-repair: how many of those objects were completely
1554 healthy, before any repair
1555 count-objects-unhealthy-pre-repair: how many were damaged in some way
1556 count-objects-healthy-post-repair: how many of those objects were completely
1557 healthy, after any repair
1558 count-objects-unhealthy-post-repair: how many were damaged in some way
1560 count-repairs-attempted: repairs were attempted on this many objects.
1561 count-repairs-successful: how many repairs resulted in healthy objects
1562 count-repairs-unsuccessful: how many repairs resulted did not results in
1563 completely healthy objects
1564 count-corrupt-shares-pre-repair: how many shares were found to have
1565 corruption, summed over all objects
1566 examined, before any repair
1567 count-corrupt-shares-post-repair: how many shares were found to have
1568 corruption, summed over all objects
1569 examined, after any repair
1570 list-corrupt-shares: a list of "share identifiers", one for each share
1571 that was found to be corrupt (before any repair).
1572 Each share identifier is a list of (serverid,
1573 storage_index, sharenum).
1574 list-remaining-corrupt-shares: like list-corrupt-shares, but mutable shares
1575 that were successfully repaired are not
1576 included. These are shares that need
1577 manual processing. Since immutable shares
1578 cannot be modified by clients, all corruption
1579 in immutable shares will be listed here.
1580 list-unhealthy-files: a list of (pathname, check-results) tuples, for
1581 each file that was not fully healthy. 'pathname' is
1582 relative to the directory on which deep-check was
1583 invoked. The 'check-results' field is the same as
1584 that returned by t=check&repair=true&output=JSON,
1586 stats: a dictionary with the same keys as the t=start-deep-stats command
1589 ``POST $URL?t=stream-deep-check&repair=true``
1591 This triggers a recursive walk of all files and directories, performing a
1592 t=check&repair=true on each one. For each unique object (duplicates are
1593 skipped), a single line of JSON is emitted to the HTTP response channel (or
1594 an error indication). When the walk is complete, a final line of JSON is
1595 emitted which contains the accumulated file-size/count "deep-stats" data.
1597 This emits the same data as t=stream-deep-check (without the repair=true),
1598 except that the "check-results" field is replaced with a
1599 "check-and-repair-results" field, which contains the keys returned by
1600 t=check&repair=true&output=json (i.e. repair-attempted, repair-successful,
1601 pre-repair-results, and post-repair-results). The output does not contain
1602 the summary dictionary that is provied by t=start-deep-check&repair=true
1603 (the one with count-objects-checked and list-unhealthy-files), since the
1604 receiving client is expected to calculate those values itself from the
1605 stream of per-object check-and-repair-results.
1607 Note that the "ERROR:" indication will only be emitted if traversal stops,
1608 which will only occur if an unrecoverable directory is encountered. If a
1609 file or directory repair fails, the traversal will continue, and the repair
1610 failure will be indicated in the JSON data (in the "repair-successful" key).
1612 ``POST $DIRURL?t=start-manifest`` (must add &ophandle=XYZ)
1614 This operation generates a "manfest" of the given directory tree, mostly
1615 for debugging. This is a table of (path, filecap/dircap), for every object
1616 reachable from the starting directory. The path will be slash-joined, and
1617 the filecap/dircap will contain a link to the object in question. This page
1618 gives immediate access to every object in the virtual filesystem subtree.
1620 This operation uses the same ophandle= mechanism as deep-check. The
1621 corresponding /operations/$HANDLE page has three different forms. The
1622 default is output=HTML.
1624 If output=text is added to the query args, the results will be a text/plain
1625 list. The first line is special: it is either "finished: yes" or "finished:
1626 no"; if the operation is not finished, you must periodically reload the
1627 page until it completes. The rest of the results are a plaintext list, with
1628 one file/dir per line, slash-separated, with the filecap/dircap separated
1631 If output=JSON is added to the queryargs, then the results will be a
1632 JSON-formatted dictionary with six keys. Note that because large directory
1633 structures can result in very large JSON results, the full results will not
1634 be available until the operation is complete (i.e. until output["finished"]
1637 finished (bool): if False then you must reload the page until True
1638 origin_si (base32 str): the storage index of the starting point
1639 manifest: list of (path, cap) tuples, where path is a list of strings.
1640 verifycaps: list of (printable) verify cap strings
1641 storage-index: list of (base32) storage index strings
1642 stats: a dictionary with the same keys as the t=start-deep-stats command
1645 ``POST $DIRURL?t=start-deep-size`` (must add &ophandle=XYZ)
1647 This operation generates a number (in bytes) containing the sum of the
1648 filesize of all directories and immutable files reachable from the given
1649 directory. This is a rough lower bound of the total space consumed by this
1650 subtree. It does not include space consumed by mutable files, nor does it
1651 take expansion or encoding overhead into account. Later versions of the
1652 code may improve this estimate upwards.
1654 The /operations/$HANDLE status output consists of two lines of text::
1659 ``POST $DIRURL?t=start-deep-stats`` (must add &ophandle=XYZ)
1661 This operation performs a recursive walk of all files and directories
1662 reachable from the given directory, and generates a collection of
1663 statistics about those objects.
1665 The result (obtained from the /operations/$OPHANDLE page) is a
1666 JSON-serialized dictionary with the following keys (note that some of these
1667 keys may be missing until 'finished' is True)::
1669 finished: (bool) True if the operation has finished, else False
1670 count-immutable-files: count of how many CHK files are in the set
1671 count-mutable-files: same, for mutable files (does not include directories)
1672 count-literal-files: same, for LIT files (data contained inside the URI)
1673 count-files: sum of the above three
1674 count-directories: count of directories
1675 count-unknown: count of unrecognized objects (perhaps from the future)
1676 size-immutable-files: total bytes for all CHK files in the set, =deep-size
1677 size-mutable-files (TODO): same, for current version of all mutable files
1678 size-literal-files: same, for LIT files
1679 size-directories: size of directories (includes size-literal-files)
1680 size-files-histogram: list of (minsize, maxsize, count) buckets,
1681 with a histogram of filesizes, 5dB/bucket,
1682 for both literal and immutable files
1683 largest-directory: number of children in the largest directory
1684 largest-immutable-file: number of bytes in the largest CHK file
1686 size-mutable-files is not implemented, because it would require extra
1687 queries to each mutable file to get their size. This may be implemented in
1690 Assuming no sharing, the basic space consumed by a single root directory is
1691 the sum of size-immutable-files, size-mutable-files, and size-directories.
1692 The actual disk space used by the shares is larger, because of the
1693 following sources of overhead::
1696 expansion due to erasure coding
1697 share management data (leases)
1698 backend (ext3) minimum block size
1700 ``POST $URL?t=stream-manifest``
1702 This operation performs a recursive walk of all files and directories
1703 reachable from the given starting point. For each such unique object
1704 (duplicates are skipped), a single line of JSON is emitted to the HTTP
1705 response channel (or an error indication, see below). When the walk is
1706 complete, a final line of JSON is emitted which contains the accumulated
1707 file-size/count "deep-stats" data.
1709 A CLI tool can split the response stream on newlines into "response units",
1710 and parse each response unit as JSON. Each such parsed unit will be a
1711 dictionary, and will contain at least the "type" key: a string, one of
1712 "file", "directory", or "stats".
1714 For all units that have a type of "file" or "directory", the dictionary will
1715 contain the following keys::
1717 "path": a list of strings, with the path that is traversed to reach the
1719 "cap": a write-cap URI for the file or directory, if available, else a
1721 "verifycap": a verify-cap URI for the file or directory
1722 "repaircap": an URI for the weakest cap that can still be used to repair
1724 "storage-index": a base32 storage index for the object
1726 Note that non-distributed files (i.e. LIT files) will have values of None
1727 for verifycap, repaircap, and storage-index, since these files can neither
1728 be verified nor repaired, and are not stored on the storage servers.
1730 The last unit in the stream will have a type of "stats", and will contain
1731 the keys described in the "start-deep-stats" operation, below.
1733 If any errors occur during the traversal (specifically if a directory is
1734 unrecoverable, such that further traversal is not possible), an error
1735 indication is written to the response body, instead of the usual line of
1736 JSON. This error indication line will begin with the string "ERROR:" (in all
1737 caps), and contain a summary of the error on the rest of the line. The
1738 remaining lines of the response body will be a python exception. The client
1739 application should look for the ERROR: and stop processing JSON as soon as
1740 it is seen. The line just before the ERROR: will describe the directory that
1741 was untraversable, since the manifest entry is emitted to the HTTP response
1742 body before the child is traversed.
1748 The portion of the web namespace that begins with "/uri" (and "/named") is
1749 dedicated to giving users (both humans and programs) access to the Tahoe
1750 virtual filesystem. The rest of the namespace provides status information
1751 about the state of the Tahoe node.
1753 ``GET /`` (the root page)
1755 This is the "Welcome Page", and contains a few distinct sections::
1757 Node information: library versions, local nodeid, services being provided.
1759 Filesystem Access Forms: create a new directory, view a file/directory by
1760 URI, upload a file (unlinked), download a file by
1763 Grid Status: introducer information, helper information, connected storage
1768 This page lists all active uploads and downloads, and contains a short list
1769 of recent upload/download operations. Each operation has a link to a page
1770 that describes file sizes, servers that were involved, and the time consumed
1771 in each phase of the operation.
1773 A GET of /status/?t=json will contain a machine-readable subset of the same
1774 data. It returns a JSON-encoded dictionary. The only key defined at this
1775 time is "active", with a value that is a list of operation dictionaries, one
1776 for each active operation. Once an operation is completed, it will no longer
1777 appear in data["active"] .
1779 Each op-dict contains a "type" key, one of "upload", "download",
1780 "mapupdate", "publish", or "retrieve" (the first two are for immutable
1781 files, while the latter three are for mutable files and directories).
1783 The "upload" op-dict will contain the following keys::
1785 type (string): "upload"
1786 storage-index-string (string): a base32-encoded storage index
1787 total-size (int): total size of the file
1788 status (string): current status of the operation
1789 progress-hash (float): 1.0 when the file has been hashed
1790 progress-ciphertext (float): 1.0 when the file has been encrypted.
1791 progress-encode-push (float): 1.0 when the file has been encoded and
1792 pushed to the storage servers. For helper
1793 uploads, the ciphertext value climbs to 1.0
1794 first, then encoding starts. For unassisted
1795 uploads, ciphertext and encode-push progress
1796 will climb at the same pace.
1798 The "download" op-dict will contain the following keys::
1800 type (string): "download"
1801 storage-index-string (string): a base32-encoded storage index
1802 total-size (int): total size of the file
1803 status (string): current status of the operation
1804 progress (float): 1.0 when the file has been fully downloaded
1806 Front-ends which want to report progress information are advised to simply
1807 average together all the progress-* indicators. A slightly more accurate
1808 value can be found by ignoring the progress-hash value (since the current
1809 implementation hashes synchronously, so clients will probably never see
1810 progress-hash!=1.0).
1812 ``GET /helper_status/``
1814 If the node is running a helper (i.e. if [helper]enabled is set to True in
1815 tahoe.cfg), then this page will provide a list of all the helper operations
1816 currently in progress. If "?t=json" is added to the URL, it will return a
1817 JSON-formatted list of helper statistics, which can then be used to produce
1818 graphs to indicate how busy the helper is.
1820 ``GET /statistics/``
1822 This page provides "node statistics", which are collected from a variety of
1825 load_monitor: every second, the node schedules a timer for one second in
1826 the future, then measures how late the subsequent callback
1827 is. The "load_average" is this tardiness, measured in
1828 seconds, averaged over the last minute. It is an indication
1829 of a busy node, one which is doing more work than can be
1830 completed in a timely fashion. The "max_load" value is the
1831 highest value that has been seen in the last 60 seconds.
1833 cpu_monitor: every minute, the node uses time.clock() to measure how much
1834 CPU time it has used, and it uses this value to produce
1835 1min/5min/15min moving averages. These values range from 0%
1836 (0.0) to 100% (1.0), and indicate what fraction of the CPU
1837 has been used by the Tahoe node. Not all operating systems
1838 provide meaningful data to time.clock(): they may report 100%
1839 CPU usage at all times.
1841 uploader: this counts how many immutable files (and bytes) have been
1842 uploaded since the node was started
1844 downloader: this counts how many immutable files have been downloaded
1845 since the node was started
1847 publishes: this counts how many mutable files (including directories) have
1848 been modified since the node was started
1850 retrieves: this counts how many mutable files (including directories) have
1851 been read since the node was started
1853 There are other statistics that are tracked by the node. The "raw stats"
1854 section shows a formatted dump of all of them.
1856 By adding "?t=json" to the URL, the node will return a JSON-formatted
1857 dictionary of stats values, which can be used by other tools to produce
1858 graphs of node behavior. The misc/munin/ directory in the source
1859 distribution provides some tools to produce these graphs.
1861 ``GET /`` (introducer status)
1863 For Introducer nodes, the welcome page displays information about both
1864 clients and servers which are connected to the introducer. Servers make
1865 "service announcements", and these are listed in a table. Clients will
1866 subscribe to hear about service announcements, and these subscriptions are
1867 listed in a separate table. Both tables contain information about what
1868 version of Tahoe is being run by the remote node, their advertised and
1869 outbound IP addresses, their nodeid and nickname, and how long they have
1872 By adding "?t=json" to the URL, the node will return a JSON-formatted
1873 dictionary of stats values, which can be used to produce graphs of connected
1874 clients over time. This dictionary has the following keys::
1876 ["subscription_summary"] : a dictionary mapping service name (like
1877 "storage") to an integer with the number of
1878 clients that have subscribed to hear about that
1880 ["announcement_summary"] : a dictionary mapping service name to an integer
1881 with the number of servers which are announcing
1883 ["announcement_distinct_hosts"] : a dictionary mapping service name to an
1884 integer which represents the number of
1885 distinct hosts that are providing that
1886 service. If two servers have announced
1887 FURLs which use the same hostnames (but
1888 different ports and tubids), they are
1889 considered to be on the same host.
1892 Static Files in /public_html
1893 ============================
1895 The web-API server will take any request for a URL that starts with /static
1896 and serve it from a configurable directory which defaults to
1897 $BASEDIR/public_html . This is configured by setting the "[node]web.static"
1898 value in $BASEDIR/tahoe.cfg . If this is left at the default value of
1899 "public_html", then http://127.0.0.1:3456/static/subdir/foo.html will be
1900 served with the contents of the file $BASEDIR/public_html/subdir/foo.html .
1902 This can be useful to serve a javascript application which provides a
1903 prettier front-end to the rest of the Tahoe web-API.
1906 Safety and Security Issues -- Names vs. URIs
1907 ============================================
1909 Summary: use explicit file- and dir- caps whenever possible, to reduce the
1910 potential for surprises when the filesystem structure is changed.
1912 Tahoe provides a mutable filesystem, but the ways that the filesystem can
1913 change are limited. The only thing that can change is that the mapping from
1914 child names to child objects that each directory contains can be changed by
1915 adding a new child name pointing to an object, removing an existing child name,
1916 or changing an existing child name to point to a different object.
1918 Obviously if you query Tahoe for information about the filesystem and then act
1919 to change the filesystem (such as by getting a listing of the contents of a
1920 directory and then adding a file to the directory), then the filesystem might
1921 have been changed after you queried it and before you acted upon it. However,
1922 if you use the URI instead of the pathname of an object when you act upon the
1923 object, then the only change that can happen is if the object is a directory
1924 then the set of child names it has might be different. If, on the other hand,
1925 you act upon the object using its pathname, then a different object might be in
1926 that place, which can result in more kinds of surprises.
1928 For example, suppose you are writing code which recursively downloads the
1929 contents of a directory. The first thing your code does is fetch the listing
1930 of the contents of the directory. For each child that it fetched, if that
1931 child is a file then it downloads the file, and if that child is a directory
1932 then it recurses into that directory. Now, if the download and the recurse
1933 actions are performed using the child's name, then the results might be
1934 wrong, because for example a child name that pointed to a sub-directory when
1935 you listed the directory might have been changed to point to a file (in which
1936 case your attempt to recurse into it would result in an error and the file
1937 would be skipped), or a child name that pointed to a file when you listed the
1938 directory might now point to a sub-directory (in which case your attempt to
1939 download the child would result in a file containing HTML text describing the
1942 If your recursive algorithm uses the uri of the child instead of the name of
1943 the child, then those kinds of mistakes just can't happen. Note that both the
1944 child's name and the child's URI are included in the results of listing the
1945 parent directory, so it isn't any harder to use the URI for this purpose.
1947 The read and write caps in a given directory node are separate URIs, and
1948 can't be assumed to point to the same object even if they were retrieved in
1949 the same operation (although the web-API server attempts to ensure this
1950 in most cases). If you need to rely on that property, you should explicitly
1951 verify it. More generally, you should not make assumptions about the
1952 internal consistency of the contents of mutable directories. As a result
1953 of the signatures on mutable object versions, it is guaranteed that a given
1954 version was written in a single update, but -- as in the case of a file --
1955 the contents may have been chosen by a malicious writer in a way that is
1956 designed to confuse applications that rely on their consistency.
1958 In general, use names if you want "whatever object (whether file or
1959 directory) is found by following this name (or sequence of names) when my
1960 request reaches the server". Use URIs if you want "this particular object".
1966 Tahoe uses both mutable and immutable files. Mutable files can be created
1967 explicitly by doing an upload with ?mutable=true added, or implicitly by
1968 creating a new directory (since a directory is just a special way to
1969 interpret a given mutable file).
1971 Mutable files suffer from the same consistency-vs-availability tradeoff that
1972 all distributed data storage systems face. It is not possible to
1973 simultaneously achieve perfect consistency and perfect availability in the
1974 face of network partitions (servers being unreachable or faulty).
1976 Tahoe tries to achieve a reasonable compromise, but there is a basic rule in
1977 place, known as the Prime Coordination Directive: "Don't Do That". What this
1978 means is that if write-access to a mutable file is available to several
1979 parties, then those parties are responsible for coordinating their activities
1980 to avoid multiple simultaneous updates. This could be achieved by having
1981 these parties talk to each other and using some sort of locking mechanism, or
1982 by serializing all changes through a single writer.
1984 The consequences of performing uncoordinated writes can vary. Some of the
1985 writers may lose their changes, as somebody else wins the race condition. In
1986 many cases the file will be left in an "unhealthy" state, meaning that there
1987 are not as many redundant shares as we would like (reducing the reliability
1988 of the file against server failures). In the worst case, the file can be left
1989 in such an unhealthy state that no version is recoverable, even the old ones.
1990 It is this small possibility of data loss that prompts us to issue the Prime
1991 Coordination Directive.
1993 Tahoe nodes implement internal serialization to make sure that a single Tahoe
1994 node cannot conflict with itself. For example, it is safe to issue two
1995 directory modification requests to a single tahoe node's web-API server at the
1996 same time, because the Tahoe node will internally delay one of them until
1997 after the other has finished being applied. (This feature was introduced in
1998 Tahoe-1.1; back with Tahoe-1.0 the web client was responsible for serializing
1999 web requests themselves).
2001 For more details, please see the "Consistency vs Availability" and "The Prime
2002 Coordination Directive" sections of `mutable.rst <../specifications/mutable.rst>`_.
2008 Gateway nodes may find it necessary to prohibit access to certain files. The
2009 web-API has a facility to block access to filecaps by their storage index,
2010 returning a 403 "Forbidden" error instead of the original file.
2012 This blacklist is recorded in $NODEDIR/access.blacklist, and contains one
2013 blocked file per line. Comment lines (starting with ``#``) are ignored. Each
2014 line consists of the storage-index (in the usual base32 format as displayed
2015 by the "More Info" page, or by the "tahoe debug dump-cap" command), followed
2016 by whitespace, followed by a reason string, which will be included in the 403
2017 error message. This could hold a URL to a page that explains why the file is
2018 blocked, for example.
2020 So for example, if you found a need to block access to a file with filecap
2021 ``URI:CHK:n7r3m6wmomelk4sep3kw5cvduq:os7ijw5c3maek7pg65e5254k2fzjflavtpejjyhshpsxuqzhcwwq:3:20:14861``,
2022 you could do the following::
2024 tahoe debug dump-cap URI:CHK:n7r3m6wmomelk4sep3kw5cvduq:os7ijw5c3maek7pg65e5254k2fzjflavtpejjyhshpsxuqzhcwwq:3:20:14861
2025 -> storage index: whpepioyrnff7orecjolvbudeu
2026 echo "whpepioyrnff7orecjolvbudeu my puppy told me to" >>$NODEDIR/access.blacklist
2027 tahoe restart $NODEDIR
2028 tahoe get URI:CHK:n7r3m6wmomelk4sep3kw5cvduq:os7ijw5c3maek7pg65e5254k2fzjflavtpejjyhshpsxuqzhcwwq:3:20:14861
2029 -> error, 403 Access Prohibited: my puppy told me to
2031 The ``access.blacklist`` file will be checked each time a file or directory
2032 is accessed: the file's ``mtime`` is used to decide whether it need to be
2033 reloaded. Therefore no node restart is necessary when creating the initial
2034 blacklist, nor when adding second, third, or additional entries to the list.
2035 When modifying the file, be careful to update it atomically, otherwise a
2036 request may arrive while the file is only halfway written, and the partial
2037 file may be incorrectly parsed.
2039 The blacklist is applied to all access paths (including SFTP, FTP, and CLI
2040 operations), not just the web-API. The blacklist also applies to directories.
2041 If a directory is blacklisted, the gateway will refuse access to both that
2042 directory and any child files/directories underneath it, when accessed via
2043 "DIRCAP/SUBDIR/FILENAME" -style URLs. Users who go directly to the child
2044 file/dir will bypass the blacklist.
2046 The node will log the SI of the file being blocked, and the reason code, into
2047 the ``logs/twistd.log`` file.
2050 .. [1] URLs and HTTP and UTF-8, Oh My
2052 HTTP does not provide a mechanism to specify the character set used to
2053 encode non-ASCII names in URLs
2054 (`RFC3986#2.1 <https://tools.ietf.org/html/rfc3986#section-2.1>`_).
2055 We prefer the convention that the ``filename=`` argument shall be a
2056 URL-escaped UTF-8 encoded Unicode string.
2057 For example, suppose we want to provoke the server into using a filename of
2058 "f i a n c e-acute e" (i.e. f i a n c U+00E9 e). The UTF-8 encoding of this
2059 is 0x66 0x69 0x61 0x6e 0x63 0xc3 0xa9 0x65 (or "fianc\\xC3\\xA9e", as python's
2060 ``repr()`` function would show). To encode this into a URL, the non-printable
2061 characters must be escaped with the urlencode ``%XX`` mechanism, giving
2062 us "fianc%C3%A9e". Thus, the first line of the HTTP request will be
2063 "``GET /uri/CAP...?save=true&filename=fianc%C3%A9e HTTP/1.1``". Not all
2064 browsers provide this: IE7 by default uses the Latin-1 encoding, which is
2065 "fianc%E9e" (although it has a configuration option to send URLs as UTF-8).
2067 The response header will need to indicate a non-ASCII filename. The actual
2068 mechanism to do this is not clear. For ASCII filenames, the response header
2071 Content-Disposition: attachment; filename="english.txt"
2073 If Tahoe were to enforce the UTF-8 convention, it would need to decode the
2074 URL argument into a Unicode string, and then encode it back into a sequence
2075 of bytes when creating the response header. One possibility would be to use
2076 unencoded UTF-8. Developers suggest that IE7 might accept this::
2078 #1: Content-Disposition: attachment; filename="fianc\xC3\xA9e"
2079 (note, the last four bytes of that line, not including the newline, are
2080 0xC3 0xA9 0x65 0x22)
2082 `RFC2231#4 <https://tools.ietf.org/html/rfc2231#section-4>`_
2083 (dated 1997): suggests that the following might work, and
2084 `some developers have reported <http://markmail.org/message/dsjyokgl7hv64ig3>`_
2085 that it is supported by Firefox (but not IE7)::
2087 #2: Content-Disposition: attachment; filename*=utf-8''fianc%C3%A9e
2089 My reading of `RFC2616#19.5.1 <https://tools.ietf.org/html/rfc2616#section-19.5.1>`_
2090 (which defines Content-Disposition) says that the filename= parameter is
2091 defined to be wrapped in quotes (presumably to allow spaces without breaking
2092 the parsing of subsequent parameters), which would give us::
2094 #3: Content-Disposition: attachment; filename*=utf-8''"fianc%C3%A9e"
2096 However this is contrary to the examples in the email thread listed above.
2098 Developers report that IE7 (when it is configured for UTF-8 URL encoding,
2099 which is not the default in Asian countries), will accept::
2101 #4: Content-Disposition: attachment; filename=fianc%C3%A9e
2103 However, for maximum compatibility, Tahoe simply copies bytes from the URL
2104 into the response header, rather than enforcing the UTF-8 convention. This
2105 means it does not try to decode the filename from the URL argument, nor does
2106 it encode the filename into the response header.