module ActionDispatch::Http::Cache::Response
def etag=(weak_validators)
Weak ETags are what we almost always need, so they're the default.
support strong ETags and will ignore weak ETags entirely.
through a PDF file or scrubbing through a video. Some CDNs only
browser or proxy cache to support +Range+ requests, useful for paging
Strong ETags are considered byte-for-byte identical. They allow a
is viewing.
pages where we don't care about exact equality, just what the user
byte-for-byte identical. This is perfect for browser caching of HTML
Weak ETags are considered to be semantically equivalent but not
current. Big savings in request time and network bandwidth.
with no body, letting the browser or proxy know that their cache is
matches the current ETag, we can return a 304 Not Modified response
requests, the +If-None-Match+ header is set to the cached ETag. If it
and proxies may cache the response, keyed on the ETag. On subsequent
This method sets a weak ETag validator on the response so browsers
def etag=(weak_validators) self.weak_etag = weak_validators end