Fix negative_caching_lifetime being overridden by ttl-in-cache#12665
Merged
bneradt merged 1 commit intoapache:masterfrom Nov 20, 2025
Merged
Fix negative_caching_lifetime being overridden by ttl-in-cache#12665bneradt merged 1 commit intoapache:masterfrom
bneradt merged 1 commit intoapache:masterfrom
Conversation
When both negative_caching_lifetime and cache.config ttl-in-cache are configured, ttl-in-cache was incorrectly overriding negative_caching_lifetime for negative responses (404, 403, 500, etc.). This caused negative responses to be cached for the ttl-in-cache duration instead of the intended negative_caching_lifetime. The fix modifies what_is_document_freshness() to skip the ttl-in-cache check for negatively cached responses.
bneradt
force-pushed
the
fix_negative_caching
branch
from
c640150 to
8c9b11d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When both negative_caching_lifetime and cache.config ttl-in-cache are configured, ttl-in-cache was incorrectly taking precedence for negative responses (404, 403, 500, etc.). This caused negative responses to be cached for the ttl-in-cache duration instead of the intended shorter negative_caching_lifetime. The fix modifies what_is_document_freshness() to skip the ttl-in-cache check for negatively cached responses, allowing them to use the Expires header set by negative_caching_lifetime instead.
For Review
Configuring github to ignore whitespace is helpful in viewing this patch.