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
CacheFilter doesn't fully implement the algorithms specified in RFC7234§4.2 to calculate freshness lifetime and age, based on the date, age, and expires response headers, the max-age and s-maxage response cache directives, and the max-age request cache directives. The RFC-specified freshness and age algorithms must be fully implemented. This must be fixed before CacheFilter can be appropriate for production deployment.
The text was updated successfully, but these errors were encountered:
The time at which responses are received is recorded, and stored with cached responses as response_time. When a response is served from cache, response_time and other headers are used to correctly calculate the age of the cached response.
Risk Level: Low
Testing: Unit tests.
Docs Changes: N/A
Release Notes: N/A
Fixes#9859Fixes#12140
Signed-off-by: Yosry Ahmed <yosryahmed@google.com>
CacheFilter doesn't fully implement the algorithms specified in RFC7234§4.2 to calculate freshness lifetime and age, based on the date, age, and expires response headers, the max-age and s-maxage response cache directives, and the max-age request cache directives. The RFC-specified freshness and age algorithms must be fully implemented. This must be fixed before CacheFilter can be appropriate for production deployment.
The text was updated successfully, but these errors were encountered: