[tahoe-lafs-trac-stream] [Tahoe-LAFS] #3767: Potential issues with `POST /v1/lease/<share-index>`

[Tahoe-LAFS]

#3767: Potential issues with `POST /v1/lease/<share-index>`
----------------------+---------------------------------------
 Reporter:  itamarst  |          Owner:  exarkun
     Type:  task      |         Status:  new
 Priority:  normal    |      Milestone:  HTTP Storage Protocol
Component:  unknown   |        Version:  n/a
 Keywords:            |  Launchpad Bug:
----------------------+---------------------------------------
 "If there are no shares for the given ``storage_index`` then ``NOT FOUND``
 is returned."

 1. Does this mean... the data wasn't uploaded? The data was uploaded but
 expired? The bucket was created with 0 shares (this seems like it should
 be disallowed)?
 2. This is given same status code, 404, as the renew secret being wrong,
 but it seems rather different? Wrong secret is not the same thing as any
 variant of "that secret is good, but there is no data". "410 Gone" for no
 data, maybe?


 Can you also expand the bit about mutables? Why is mutable data even
 happening here? Can there be a different response code for the mutable
 case (a redirect?).

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3767>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage