Precondition failed #66
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
|
Changes Unknown when pulling 4416f03 on precondition-failed into * on master*. |
|
Needs a rebase |
added 2 commits
August 10, 2016 17:10
This is a more appropriate name for the error message. HTTP 412 status codes can arise for precondition failures other than etag issues, and not all etag issues are correctly characterized as mismatches. Closes #63.
Reintroduces `Ldp::ETagMismatch` as an alias to `PreconditionFailed` for backwards compatibility. Revert this to end support for the old name.
no-reply
force-pushed
the
precondition-failed
branch
from
4416f03 to
40dfa63
Compare
|
✅ |
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.
No description provided.