You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
Whenever POST to Object-URL is used to create a new resource (e.g. add a file) it should return 201.
The text was updated successfully, but these errors were encountered: