Skip to content
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

fix: always evaluate if-match headers when setting content, not just … #1797

Merged
merged 2 commits into from
Feb 7, 2024

Conversation

paulcwarren
Copy link
Owner

@paulcwarren paulcwarren commented Feb 2, 2024

…when content exists

Fixes #1795

@paulcwarren paulcwarren marked this pull request as draft February 2, 2024 05:02
@paulcwarren paulcwarren marked this pull request as ready for review February 7, 2024 05:27
@paulcwarren paulcwarren merged commit 23782f0 into main Feb 7, 2024
6 checks passed
@paulcwarren paulcwarren deleted the fix/issue-1795 branch February 7, 2024 05:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

If-Match HTTP header gets ignored by a concurrent PUT after DELETE on the content of an entity
1 participant