-
Notifications
You must be signed in to change notification settings - Fork 834
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
POSTing multiple documents #131
Comments
I think this is correct, or at least it's how I implemented it in my json-api project. +1 to making it a MUST. |
Since the server MUST return a Location header for the newly created document, how should that be formatted in the case of multiple new documents? If it is a multi-document Location, how do you resolve that with an individually identifying href for each document in the response, since they MUST match? |
How about this: The server MUST return a Location header which represents the location of the newly created resource(s)? For a single document:
For multiple:
|
#202 is a superset of this. |
It seems that the spec is setup to support POSTing multiple documents in one request : #66.
I'd like to document these rules in the
Creating a Document
section.Is it a MUST or a MAY that the server support creating multiple documents in this way? A MUST seems to make most sense. I'll submit a PR once this is clear.
The text was updated successfully, but these errors were encountered: