Description
DebugProbe currently provides built-in masking for a small set of sensitive headers such as:
- Authorization
- Cookie
- Set-Cookie
While this covers common scenarios, many applications use custom headers, query parameters, and request body fields that may contain sensitive information.
DebugProbe should provide a configurable redaction system that allows users to define additional values that should be masked before traces are stored or displayed.
Current Behavior
Only predefined sensitive headers are automatically masked.
Custom values such as:
- X-Api-Key
- X-Auth-Token
- api_key
- access_token
- password
- refreshToken
may still appear in captured traces.
Expected Behavior
Users should be able to configure additional values that DebugProbe automatically redacts.
Result
After this change: #86 #87 #88
- sensitive application-specific values are protected
- DebugProbe becomes safer to use in real-world environments
- users gain full control over redaction behavior
- security and privacy are improved without reducing debugging capabilities
Description
DebugProbe currently provides built-in masking for a small set of sensitive headers such as:
While this covers common scenarios, many applications use custom headers, query parameters, and request body fields that may contain sensitive information.
DebugProbe should provide a configurable redaction system that allows users to define additional values that should be masked before traces are stored or displayed.
Current Behavior
Only predefined sensitive headers are automatically masked.
Custom values such as:
may still appear in captured traces.
Expected Behavior
Users should be able to configure additional values that DebugProbe automatically redacts.
Result
After this change: #86 #87 #88