Cache browser redaction within requests - #77
Merged
Conversation
alexandrefimov
deleted the
perf/request-local-browser-redaction-cache
branch
September 1, 2026 11:53
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.
Reuse exact browser-redaction results only during one GET request. The cache is bounded, keeps all existing redaction options in its key, skips explicit credential environments, and is discarded before the next request.\n\nThis removes repeated regex work in Online History without weakening the browser safety boundary.\n\nChecks:\n- 494 focused web, Online History, and safety tests\n- full suite: 4,781 passed and 19 skipped; sandbox-only localhost bind failures rerun outside sandbox: 16 passed\n- Ruff check and format\n- public docs, distribution, and staged safety audits\n- git diff --check