[
https://issues.apache.org/jira/browse/HTTPCLIENT-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17720997#comment-17720997
]
Arturo Bernal commented on HTTPCLIENT-2273:
-------------------------------------------
Thank you [~reschke]
One doubt that I came cross its about the use of field-names as arguments in
the no-cache directive, as described in the RFC.
Is it valid to use field-names as arguments in the no-cache directive like
this: {{{}no-cache="Set-Cookie, Content-Language"{}}}? If so, can you please
provide some clarification on how this should be handled in terms of
revalidation and caching behavior?
Thank you in advance for your assistance,
> 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 9111.
> 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 either excluded from a
> subsequent response or revalidated with the origin server, as per RFC 9111
> requirements. This allows an origin server to prevent the reuse 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 (qualified form).
> # When specified header fields are present in a cached response, either: a.
> Optionally attempt to revalidate the response with the origin server and
> update or remove the specified header fields as needed, or b. Exclude the
> specified header fields from the subsequent response.
> # 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: [email protected]
For additional commands, e-mail: [email protected]
