[ 
https://issues.apache.org/jira/browse/HTTPCLIENT-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17720996#comment-17720996
 ] 

Oleg Kalnichevski commented on HTTPCLIENT-2273:
-----------------------------------------------

[~arturobernalg] Ah [sigh], Welcome to every day business of HttpComponents 
project. 

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. 

Oleg

> 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: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org

Reply via email to