ExternalVendorCode/tahoe-lafs
1
0
Fork 0
mirror of https://github.com/tahoe-lafs/tahoe-lafs.git synced 2025-05-02 17:12:59 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Switch to PATCH.

Browse Source
This commit is contained in:
Itamar Turner-Trauring 2021-09-28 10:34:57 -04:00
parent eb5b6c557e
commit 7e232f602a
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/proposed/http-storage-node-protocol.rst
View File

@ -482,7 +482,7 @@ The response includes ``already-have`` and ``allocated`` for two reasons:
This might be because a server has become unavailable and a remaining server needs to store more shares for the upload. This might be because a server has become unavailable and a remaining server needs to store more shares for the upload.
It could also just be that the client's preferred servers have changed. It could also just be that the client's preferred servers have changed.
``PUT /v1/immutable/:storage_index/:share_number`` ``PATCH /v1/immutable/:storage_index/:share_number``
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Write data for the indicated share. Write data for the indicated share.
@ -668,19 +668,19 @@ Immutable Data
#. Upload the content for immutable share ``7``:: #. Upload the content for immutable share ``7``::
PUT /v1/immutable/AAAAAAAAAAAAAAAA/7 PATCH /v1/immutable/AAAAAAAAAAAAAAAA/7
Content-Range: bytes 0-15/48 Content-Range: bytes 0-15/48
<first 16 bytes of share data> <first 16 bytes of share data>
200 OK 200 OK
PUT /v1/immutable/AAAAAAAAAAAAAAAA/7 PATCH /v1/immutable/AAAAAAAAAAAAAAAA/7
Content-Range: bytes 16-31/48 Content-Range: bytes 16-31/48
<second 16 bytes of share data> <second 16 bytes of share data>
200 OK 200 OK
PUT /v1/immutable/AAAAAAAAAAAAAAAA/7 PATCH /v1/immutable/AAAAAAAAAAAAAAAA/7
Content-Range: bytes 32-47/48 Content-Range: bytes 32-47/48
<final 16 bytes of share data> <final 16 bytes of share data>