Skip to content
New issue

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

POST to Object-URL should return 201 in some circumstances #17

Open
richard-jones opened this issue Jan 29, 2020 · 2 comments
Open

POST to Object-URL should return 201 in some circumstances #17

richard-jones opened this issue Jan 29, 2020 · 2 comments
Assignees
Labels

Comments

@richard-jones
Copy link
Contributor

Whenever POST to Object-URL is used to create a new resource (e.g. add a file) it should return 201.

@richard-jones
Copy link
Contributor Author

In some cases, POST creates multiple resources (e.g. through ByReferece) and this doesn't work in using the location header, so in those cases we probably just need to omit it.

@richard-jones
Copy link
Contributor Author

richard-jones commented Jul 15, 2020

Having read around this, it is not obvious that 201 is the right response code here, 200 seems equally acceptable, since the resource you are POSTing to already exists, and we are just appending data to it. Therefore, I do not propose to make this change.

  • For POST creating multiple resources, I will clarify in the spec that Location should only be returned when binary content is actually sent to the server, which absolves us from dealing with it during ByReference and MD+BR requests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants