You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
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.
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)
The text was updated successfully, but these errors were encountered: