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
The easiest solution is probably to have a flag that disables outputting headers (which are the most likely location of secrets, tokens, api keys, cookies etc.)
A more advanced solution could detect and mask based on high entropy.
Already existing or connected issues / PRs (optional)
No response
The text was updated successfully, but these errors were encountered:
Honestly, it sounds like something unlikely to be developed in the current k6/http module directly from the k6 core team. At the moment the demand is not so high to justify the complexity it would bring to the API.
If you plan to contribute, we might consider it and discuss together an API.
Feature Description
Obfuscate or remove secrets in debug output, eg: the Api-Key value below has been replaced with
************
:Suggested Solution (optional)
The easiest solution is probably to have a flag that disables outputting headers (which are the most likely location of secrets, tokens, api keys, cookies etc.)
A more advanced solution could detect and mask based on high entropy.
Already existing or connected issues / PRs (optional)
No response
The text was updated successfully, but these errors were encountered: