From: maximiliancw <redacted>
Date: Fri, 9 Jan 2026 15:57:49 +0000 (+0100)
Subject: Clarify max_scan_chars behavior for secrets detection; Added notes on detection limit... 
X-Git-Url: http://git.99rst.org/?a=commitdiff_plain;h=704f913989ce7c36221d9925dd2adf4b50c19bba;p=sgasser-llm-shield.git

Clarify max_scan_chars behavior for secrets detection; Added notes on detection limits and performance implications
---

diff --git a/config.example.yaml b/config.example.yaml
index 3ac44d6..abfede7 100644
--- a/config.example.yaml
+++ b/config.example.yaml
@@ -125,7 +125,9 @@ secrets_detection:
     # - BEARER_TOKEN
 
   # Maximum characters to scan per request (performance limit)
-  # Set to 0 to scan entire request (not recommended for large payloads)
+  # Note: Secrets placed after this limit won't be detected.
+  # Set to 0 to scan entire request (full coverage, but slower for large payloads)
+  # The 200KB default covers typical use cases
   max_scan_chars: 200000
 
   # Placeholder format for redaction (only used if action: redact)