-
-
Notifications
You must be signed in to change notification settings - Fork 59
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
Tracking request parameters #51
Comments
Mainly because of sensitive data we do not want to be responsible off which lands in our database. If you have a way to filter out all the sensitive data the PR is more than welcome. |
Aren't headers sensitive in the same way? 🤔 I think a good way to filter sensitive data within request parameters is to filter parameters whose name contains words like Same thing with headers (if this is not the case already), headers like |
They certainly are, but less common to contain user data that gets sent over. That being said, you could recycle the blacklist so the user itself has control over this, this list is being used when receiving headers Config: Function to filter: Line 215 in cedbe1b
A PR is welcome for this 😎 |
Will create a pr when I find the time, I could have needed this in a view cases for debugging already 😅 |
Hi, everyone! I wondered if there is a reason why the request parameters are not logged. This can be very usefull in some cases. (Would do a pr if this would be accepted)
The text was updated successfully, but these errors were encountered: