Set Cache-Control to no-store on paths containing %2F/%5C/%2E - #2018
Open
svpernova09 wants to merge 1 commit into
Open
Set Cache-Control to no-store on paths containing %2F/%5C/%2E#2018svpernova09 wants to merge 1 commit into
svpernova09 wants to merge 1 commit into
Conversation
svpernova09
requested review from
derickr,
saundefined,
sgolemon and
sy-records
as code owners
September 14, 2026 14:46
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
1 participant
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.
We currently have a CDN issue that can poison our caches because of how the CDN creates cache keys from paths, resulting in
/onwww.php.netbeing cached as a redirect.This patch catches those requests and sets
Cache-Control: no-storeheader so they won't be cached, but other legitimate redirects or 404s will be.Once this lands and is tested, we can remove the current workaround edge rules, which set cache time to 0 on all 301, 302, and 404 response codes.
I have opened a support ticket with Bunny to address the issue.