fix: Update the session-download API to use POST with custom verb #2635
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a follow-up to #2483.
Now we should use the
POST
HTTP method with a custom verb following the resource identifier when designing a REST API.Some references about REST API designs:
This PR also adds the
DeprecatedAPI
error to guide the API users to use the POST HTTP method, and refactorsQueryNotImplemented
(503 Service Unavailable) toNotImplementedAPI
(400 Bad Request) in analogy.Checklist: (if applicable)