[HTTPCLIENT-2273] Improve handling of "no-cache" directive with specified header fields

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 5.4-alpha1
• Assignee: Unassigned
• Reporter: Arturo Bernal
• Created: 08/May/23 19:38
• Updated: 21/Aug/23 08:54
• Resolved: 14/May/23 09:39

Description

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.

Issue Links

• is related to: HTTPCLIENT-1953 HTTP Response is not cached with Cache-Control: no-cache header