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

Clarification on the use of ETag in 4.1. Conditional Retrieval #9

Open
madsfreek opened this issue May 26, 2014 · 0 comments
Open

Clarification on the use of ETag in 4.1. Conditional Retrieval #9

madsfreek opened this issue May 26, 2014 · 0 comments
Assignees
Labels

Comments

@madsfreek
Copy link

"4.1. Conditional Retrieval" reads:

Upon a successful response the responder MUST return an ETag header
and MAY return a Last-Modified header as well.  Requesters SHOULD use
either or both, with the ETag being preferred, in any subsequent
requests for the same resource.

RFC2616 says in 13.3.4:

If an entity tag has been provided by the origin server, MUST
use that entity tag in any cache-conditional request (using If-
Match or If-None-Match).

Ie. it is mandatory to use the ETag if provided and "2.5. Response Headers" mandates it's
provision.

So 4.1 should read:

"Upon a successful response the responder MUST return an ETag header and MAY return a Last-Modified header as well. Requesters SHOULD use the ETag or both, in any subsequent requests for the same resource."

Repository owner locked and limited conversation to collaborators Jun 11, 2014
@iay iay added the bug label Jun 11, 2014
@iay iay self-assigned this Jun 11, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants