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

Post request body is sent by default #903

Closed
andreasnij opened this issue Oct 16, 2019 · 2 comments
Closed

Post request body is sent by default #903

andreasnij opened this issue Oct 16, 2019 · 2 comments

Comments

@andreasnij
Copy link

andreasnij commented Oct 16, 2019

It seems that some time between the release of 2.0 and now the Sentry client started to send post data by default. That is quite a major change, since this risk sending sensitive data to the Sentry servers. I understand the some people might want this, but why is it the default? I can't find any mention of this in the documentation or how to turn it off.

By digging through the code I discovered that this was probably introduced in #807 and that it can be turned off by setting the option 'max_request_body_size' => 'none'. In times of GDPR and frequent data leaks I really think this should be the default.

@ste93cry
Copy link
Collaborator

I can't find any mention if this in the documentation or how to turn it off.

The link in the comment I posted some time ago in #807 doesn't work anymore, but the comment from @HazAT said that the docs had to be updated. It may be that it hasn't been done, however I tend to agree that request data can contain sensitive information and should not be sent by default under any circumstance

@HazAT
Copy link
Member

HazAT commented Oct 17, 2019

It's true that POST Body can contain sensitive data.
By default, our SDK doesn't send and sensitive data that is most likely to contain sensitive data like, cookies, ip address, auth headers.
This can be enabled by setting 'send_default_pii' => true.
That this part about max_request_body_size missing in the docs is a "bug" that we will fix to make it more clear.

That it wasn't part of the initial 2.0 was just a timing issue, it was planned to ship with 2.0.
Hope this explains the situation.

Edit: getsentry/sentry-docs#1281

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants