Opened at 2021-08-16T18:51:56Z
Last modified at 2021-08-19T19:03:04Z
#3763 closed task
Potential issues with `PUT /v1/lease/:storage_index` in GBS protocol — at Initial Version
| Reported by: | itamarst | Owned by: | exarkun |
|---|---|---|---|
| Priority: | normal | Milestone: | HTTP Storage Protocol |
| Component: | unknown | Version: | n/a |
| Keywords: | Cc: | ||
| Launchpad Bug: |
Description
- It says "If there are no shares for the given storage_index then do nothing and return NO CONTENT." 204 is a success code... this seems like maybe more like an error, and should therefore have 4xx code?
- What should be returned if there are shares? Anything need to be in the response body? Just 200?
- "If the renew-secret value matches an existing lease then that lease will be renewed instead." Why is this, given there exists a separate renew API endpoint? This seems like it could mask certain categories of client bugs.
Note: See
TracTickets for help on using
tickets.
