[
https://issues.apache.org/jira/browse/HTTPCLIENT-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17721062#comment-17721062
]
Julian Reschke commented on HTTPCLIENT-2273:
--------------------------------------------
bq. Please ignore all references to RFC 91xx. Presently HC conforms to RFC 72xx
and RFC 72xx only. There is no point trying to make some random bits of the
caching code conform to RFC 91xx if the rest of the project is still at the RFC
72xx conformance level.
Updates to RFCs are supposed to clarify things or fix bugs. There is only one
HTTP. Sticking to obsoleted docs is a complete waste of time.
> Improve handling of "no-cache" directive with specified header fields
> ---------------------------------------------------------------------
>
> Key: HTTPCLIENT-2273
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2273
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Reporter: Arturo Bernal
> Priority: Major
>
> Currently, the Apache HttpComponents client does not fully handle the
> "no-cache" directive with specified header fields as outlined in RFC 7234.
> This may lead to incorrect caching behavior when the "no-cache" directive is
> used with specific header fields.
> The goal of this ticket is to enhance the handling of the "no-cache"
> directive to ensure that specified header fields are not sent in a response
> to a subsequent request without successful revalidation with the origin
> server. This allows an origin server to prevent the re-use of certain header
> fields in a response, while still allowing caching of the rest of the
> response.
> To achieve this, the following changes should be made:
> # Update the caching module to identify and handle "no-cache" directives
> with specified header fields.
> # Revalidate the response with the origin server when the specified header
> fields are present in a cached response, to ensure that they are not reused
> without successful revalidation.
> # Ensure that the rest of the response is still cacheable when the specified
> header fields are present, as long as the response complies with other
> caching requirements.
--
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
