mirror of
https://github.com/tahoe-lafs/tahoe-lafs.git
synced 2025-02-21 18:06:46 +00:00
write share data
This commit is contained in:
parent
b6572e2856
commit
5b35f591f1
@ -149,6 +149,11 @@ For example::
|
|||||||
{"already_have": [1, ...],
|
{"already_have": [1, ...],
|
||||||
"allocated": {7: "bucket_id", ...}}
|
"allocated": {7: "bucket_id", ...}}
|
||||||
|
|
||||||
|
``PUT /v1/buckets/:bucket_id``
|
||||||
|
|
||||||
|
Write the share data to the indicated bucket.
|
||||||
|
The request body is the raw share data (i.e., ``application/octet-stream``).
|
||||||
|
|
||||||
.. [#] What are best practices regarding TLS version?
|
.. [#] What are best practices regarding TLS version?
|
||||||
Would a policy of "use the newest version shared between the two endpoints" be better?
|
Would a policy of "use the newest version shared between the two endpoints" be better?
|
||||||
Is it necessary to specify more than a TLS version number here?
|
Is it necessary to specify more than a TLS version number here?
|
||||||
|
Loading…
x
Reference in New Issue
Block a user