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

Freshening responses with more than one validator #659

Closed
mnot opened this issue Jan 7, 2021 · 1 comment · Fixed by #666
Closed

Freshening responses with more than one validator #659

mnot opened this issue Jan 7, 2021 · 1 comment · Fixed by #666

Comments

@mnot
Copy link
Member

mnot commented Jan 7, 2021

4.3.4 Freshening Stored Responses upon Validation is silent about what to do when there's more than one validator in the message. Freshening responses with HEAD (just below) specifies that any validators must match.

(use of 'match' there is a bit fuzzy, should probably link to where it's defined)

@royfielding
Copy link
Member

I think this section would be better written in terms of entity tags and dates, rather than the abstract notion of strong validators. But I don't know if we have time for that.

The basic idea is that a cache might have sent several strong validators in the request and is now being told that at least some of those validators indicate valid responses, so each validator in the 304 indicates a valid response. I don't think the origin server has a preference on which one, but in general the strong etag validators should be considered first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

2 participants