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 ETag Handling #68

Open
no-reply opened this issue Aug 9, 2016 · 2 comments
Open

Fix ETag Handling #68

no-reply opened this issue Aug 9, 2016 · 2 comments

Comments

@no-reply
Copy link
Member

no-reply commented Aug 9, 2016

We have a few problems with ETag handling:

  • RFC 7232 sec. 3.1 requires us to use strong validation on If-Match, we use weak.
  • Even our weak validation is incorrect; see RFC 7232 sec. 2.3.2.
  • If we use strong validation, clients will never be able to use If-Match (since we don't generate strong ETags).

Discussion of this issue within the LDP WG is in this thread.

@no-reply
Copy link
Member Author

no-reply commented Aug 9, 2016

The restriction referred to in the email thread linked above was added in https://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-24. I'm unsure whether the LDP WG ever discussed this development.

@no-reply no-reply modified the milestones: 1.0, Initial Release Aug 15, 2016
@no-reply
Copy link
Member Author

The proposed fix is to fail If-Match (Precondition Failed) for all checks.

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

No branches or pull requests

1 participant