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
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."
The text was updated successfully, but these errors were encountered:
Repository owner
locked and limited conversation to collaborators
Jun 11, 2014
"4.1. Conditional Retrieval" reads:
RFC2616 says in 13.3.4:
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."
The text was updated successfully, but these errors were encountered: