module ActionDispatch::Http::Cache::Response

#strong_etag= to provide a strong ETag validator.
Weak ETags are what we almost always need, so they're the default. Check out

ignore weak ETags entirely.
or scrubbing through a video. Some CDNs only support strong ETags and will
proxy cache to support `Range` requests, useful for paging through a PDF file
Strong ETags are considered byte-for-byte identical. They allow a browser or

care about exact equality, just what the user is viewing.
identical. This is perfect for browser caching of HTML pages where we don't
Weak ETags are considered to be semantically equivalent but not byte-for-byte

and network bandwidth.
browser or proxy know that their cache is current. Big savings in request time
ETag, we can return a `304 Not Modified` response with no body, letting the
`If-None-Match` header is set to the cached ETag. If it matches the current
may cache the response, keyed on the ETag. On subsequent requests, the
This method sets a weak ETag validator on the response so browsers and proxies

def etag=(weak_validators)
  self.weak_etag = weak_validators
end