bneradt opened a new pull request, #13913: URL: https://github.com/apache/trafficserver/pull/13913
Since #12670, a Cache-Control directive followed by unparseable content is ignored entirely. That is the right outcome for directives that permit caching, such as public or max-age: ignoring them can only make ATS cache less. For directives that restrict caching it has the opposite effect. A response with "Cache-Control: private; max-age=600" and a future Expires loses its private restriction, so ATS stores it in the shared cache and serves one user's response to other users. Before #12670, ATS kept private in this case. This patch keeps the private, no-cache, no-store, must-revalidate and proxy-revalidate directives when they are followed by unparseable content, while still ignoring malformed permissive directives. A malformed Cache-Control header can therefore only make ATS cache less than it otherwise would. This follows the RFC 9111 Section 4.2.1 guidance that conflicting directives be resolved in favor of the most restrictive one. This is independent of https://github.com/apache/trafficserver/pull/13912, which fixes the related handling of qualified directives such as private="X-User-Token". 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
