We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PUT containers
POST containers
I'm always frustrated when we're not following RFC 9110. The short definition of PUT is
Replace all current representations of the target resource with the request content.
The resource is containers, but we're far from replacing it here (since to GET containers is to obtain a list of them). We're just adding a new one.
containers
GET containers
Make it a POST. Return 201 from it with a proper Location.
POST
Location
Keep as is, it works too. Well, we need to keep it anyway in deprecated fashion.
https://www.rfc-editor.org/rfc/rfc9110.html
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is your feature request related to a problem? Please describe.
I'm always frustrated when we're not following RFC 9110. The short definition of PUT is
The resource is
containers
, but we're far from replacing it here (since toGET containers
is to obtain a list of them). We're just adding a new one.Describe the solution you'd like
Make it a
POST
. Return 201 from it with a properLocation
.Describe alternatives you've considered
Keep as is, it works too. Well, we need to keep it anyway in deprecated fashion.
Additional context
https://www.rfc-editor.org/rfc/rfc9110.html
The text was updated successfully, but these errors were encountered: