Namespace
Methods
- C
- E
- F
- I
- N
Constants
| HTTP_IF_MODIFIED_SINCE | = | "HTTP_IF_MODIFIED_SINCE" |
| HTTP_IF_NONE_MATCH | = | "HTTP_IF_NONE_MATCH" |
Instance Public methods
cache_control_directives() Link
etag_matches?(etag) Link
fresh?(response) Link
Check response freshness (Last-Modified and ETag) against request If-Modified-Since and If-None-Match conditions. If both headers are supplied, based on configuration, either ETag is preferred over Last-Modified or both are considered equally. You can adjust the preference with config.action_dispatch.strict_freshness. Reference: tools.ietf.org/html/rfc7232#section-6
# File actionpack/lib/action_dispatch/http/cache.rb, line 49 def fresh?(response) if Request.strict_freshness if if_none_match etag_matches?(response.etag) elsif if_modified_since not_modified?(response.last_modified) else false end else last_modified = if_modified_since etag = if_none_match return false unless last_modified || etag success = true success &&= not_modified?(response.last_modified) if last_modified success &&= etag_matches?(response.etag) if etag success end end
if_modified_since() Link
# File actionpack/lib/action_dispatch/http/cache.rb, line 14 def if_modified_since if since = get_header(HTTP_IF_MODIFIED_SINCE) # `If-Modified-Since` carries an HTTP-date, which per RFC 9110 may be in # any of the three legal formats (IMF-fixdate, RFC 850, or asctime). # `Time.httpdate` accepts all three; it also matches how the response side # parses `Last-Modified`/`Date`. `Time.rfc2822` only accepted IMF-fixdate. Time.httpdate(since) rescue nil end end