You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Django Silk, when SILKY_SENSITIVE_KEYS is set as an empty dictionary ({}), the expected behavior is that no values in the request body and headers should be masked, since masking should only apply to keys explicitly listed under SILKY_SENSITIVE_KEYS.
However, instead of allowing all request body values to remain visible, Django Silk incorrectly masks everything in the request body.
Expected Behavior:
If SILKY_SENSITIVE_KEYS is empty ({}), Django Silk should not mask any values in the request body.
Actual Behavior:
When SILKY_SENSITIVE_KEYS = {}, all request body values are masked, which is incorrect.
Steps to Reproduce:
Set SILKY_SENSITIVE_KEYS = {} in Django settings.
Make an API request with a request body containing various key-value pairs.
Observe that all values in the request body are masked in the Django Silk logs, even though no keys are
specified for masking.
This issue affects data visibility in logs and may lead to unexpected debugging challenges.
The text was updated successfully, but these errors were encountered:
In Django Silk, when SILKY_SENSITIVE_KEYS is set as an empty dictionary ({}), the expected behavior is that no values in the request body and headers should be masked, since masking should only apply to keys explicitly listed under SILKY_SENSITIVE_KEYS.
However, instead of allowing all request body values to remain visible, Django Silk incorrectly masks everything in the request body.
Expected Behavior:
If SILKY_SENSITIVE_KEYS is empty ({}), Django Silk should not mask any values in the request body.
Actual Behavior:
When SILKY_SENSITIVE_KEYS = {}, all request body values are masked, which is incorrect.
Steps to Reproduce:
specified for masking.
The text was updated successfully, but these errors were encountered: