Feat: Create resource with PUT instead of POST request method - #164
Open
mrkvon wants to merge 2 commits into
Open
Feat: Create resource with PUT instead of POST request method#164mrkvon wants to merge 2 commits into
mrkvon wants to merge 2 commits into
Conversation
mrkvon
force-pushed
the
feat/put-create-resource
branch
from
July 16, 2026 20:54
554de98 to
1436a48
Compare
jaxoncreed
reviewed
Jul 24, 2026
PUT will guarantee the URI of the resource. Closes o-development#16
`If-None-Match: *` header ensures resource is not overwritten. We then use HTTP status codes 200, 201, 412 to figure out what actually happened. https://solidproject.org/TR/protocol#conditional-update https://www.rfc-editor.org/info/rfc9110/#section-13.1.2
mrkvon
force-pushed
the
feat/put-create-resource
branch
from
July 25, 2026 20:30
1436a48 to
58f30df
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
PUT will guarantee the URI of the resource.
We also use HTTP Semantics to ensure an existing resource doesn't get overwritten when we don't want it to.
If-None-Match: *header ensures resource is not overwritten. We then use HTTP status codes 200, 201, 412 to figure out what actually happened. This saves us the oneDELETErequest beforePUT.https://solidproject.org/TR/protocol#conditional-update
https://www.rfc-editor.org/info/rfc9110/#section-13.1.2, because Solid servers MUST conform to RFC 9110.
The two commits are somewhat independent, so it may be meaningful not to squash them.
The second commit (using HTTP If-None-Match conditional update) is also optional. If it's not desirable, we can get rid of it.
Closes #16