200 and 201 and location headers #90
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…hen creating a resource
|
Thanks! |
|
FWIW, I did some small tweaking around the language/formatting. I think it all should be the same messaging/recommendations though. Definitely let me know if you disagree or there are mistakes. Changes here: b1cea73 |
brandur
added a commit
to brandur/heroku-http-api-design
that referenced
this pull request
Jun 5, 2021
Based on: interagent/http-api-design#90 And with the follow up that tweaked the language somewhat: b1cea73ba46e47b9fa6520e5bbedf771b066cf62
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
It is useful to return Location header post POST creation, because the caller made the request on the POST handler, not the created resource.
With PUT, the request is made on the target resource, so Lcation header can be omitted.