Arturo Bernal created HTTPCLIENT-2276:
-----------------------------------------
Summary: Implementing 'Calculating Secondary Keys with Vary' as
Per RFC 7234 for HTTP Cache Validity"
Key: HTTPCLIENT-2276
URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2276
Project: HttpComponents HttpClient
Issue Type: Improvement
Reporter: Arturo Bernal
The purpose of this ticket is to implement the method "Calculating Secondary
Keys with Vary" as described in RFC 7234, section 4.1 for HTTP Cache Validity
in our caching solution.
Currently, our solution doesn't consider the rules for matching the selecting
header fields mentioned in the RFC while validating cache. The requirement is
to match the selecting header fields from the original request and the
presented request by applying the following transformations:
# Adding or removing whitespace, where allowed in the header field's syntax.
# Combining multiple header fields with the same field name.
# Normalizing both header field values in a way that is known to have
identical semantics, according to the header field's specification (e.g.,
reordering field values when order is not significant; case-normalization,
where values are defined to be case-insensitive).
The ticket includes handling of cases where a header field is absent from a
request, it should match another request only if it is also absent there. Also,
a Vary header field-value of "*" should always fail to match.
Lastly, the implementation should handle the selection of response when
multiple selected responses are available, and the case when no selected
response is available.
This enhancement is expected to improve our cache validity check and adhere to
the standard protocol as outlined in RFC 7234.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org
