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
We are using Sentry/raven-php in our application to log user actions, such as log in and purchasing. raven-php sends all $_POST data to the sentry server, which includes things like passwords and credit card details in these cases. This is not optimal.
Looking at the source code, there is no way to filter $_POST data before it is sent, or to not send it at all. We do not want to be responsible for storing sensitive client information in our logging application, nor transmitting such information across the internet.
Can some options be added to either disable the sending of $_POST/$_GET/etc data for some requests, or to filter the data that is sent through a user supplied callback?
The text was updated successfully, but these errors were encountered:
We are using Sentry/raven-php in our application to log user actions, such as log in and purchasing.
raven-php
sends all $_POST data to the sentry server, which includes things like passwords and credit card details in these cases. This is not optimal.Looking at the source code, there is no way to filter $_POST data before it is sent, or to not send it at all. We do not want to be responsible for storing sensitive client information in our logging application, nor transmitting such information across the internet.
Can some options be added to either disable the sending of $_POST/$_GET/etc data for some requests, or to filter the data that is sent through a user supplied callback?
The text was updated successfully, but these errors were encountered: