[
https://issues.apache.org/jira/browse/HTTPCLIENT-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17726381#comment-17726381
]
Arturo Bernal commented on HTTPCLIENT-2277:
-------------------------------------------
4.2.1. Calculating Freshness Lifetime
* If the cache is shared and the s-maxage response directive ([Section
5.2.2.10|https://httpwg.org/specs/rfc9111.html#cache-response-directive.s-maxage])
is present, use its value, or
It's apparent we need to review our handling of instances when multiple values
exist for a given directive, such as multiple Cache-Control: max-age directives
or two Expires header field lines. We should employ a meticulous approach:
utilize the first occurrence, or in the absence of a clear choice, consider the
response as stale
* When there is more than one value present for a given directive (e.g., two
[Expires|https://httpwg.org/specs/rfc9111.html#field.expires] header field
lines or multiple Cache-Control: max-age directives), either the first
occurrence should be used or the response should be considered stale. If
directives conflict (e.g., both max-age and no-cache are present), the most
restrictive directive should be honored. Caches are encouraged to consider
responses that have invalid freshness information (e.g., a max-age directive
with non-integer content) to be stale.
> HttpClient Cache conformance to RFC 9111
> ----------------------------------------
>
> Key: HTTPCLIENT-2277
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2277
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: HttpCache
> Reporter: Oleg Kalnichevski
> Priority: Major
>
> Ensure HttpClient Cache conforms to RFC 9111.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
