Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

filter query params from logs #10735

Open
2 tasks done
ProfXponent opened this issue May 17, 2024 · 1 comment
Open
2 tasks done

filter query params from logs #10735

ProfXponent opened this issue May 17, 2024 · 1 comment
Labels
area/accesslogs kind/proposal a proposal that needs to be discussed.

Comments

@ProfXponent
Copy link

Welcome!

  • Yes, I've searched similar issues on GitHub and didn't find any.
  • Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you expect to see?

traefik does not provide any means of filtering sensitive query params from logs aside form redacting the entire require uri, which is not an option for many

request uris like the one below often contain sensitive data that should not be persisted to a log file

192.168.112.1 - - [17/May/2024:08:48:35 +0000] "GET /cms-api/auth/google/callback?access_token=REDACTED HTTP/1.1" 200 339 "-" "-" 1390513 "web@file" "http://web:3000" 52ms

this is a major issue and is likely compromising many traefik users already

@sdelicata sdelicata added kind/proposal a proposal that needs to be discussed. area/accesslogs and removed status/0-needs-triage labels May 23, 2024
@sdelicata
Copy link
Contributor

Hey @ProfXponent.

Thanks for your suggestion.

We are interested in this issue.
We are going to leave the status as kind/proposal to give the community time to let us know if they would like this idea.
We will reevaluate as people respond.

Conversation is time-boxed to 6 months.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/accesslogs kind/proposal a proposal that needs to be discussed.
Projects
None yet
Development

No branches or pull requests

3 participants