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
Copy file name to clipboardExpand all lines: readme.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,6 +34,8 @@ Version 2 of this module includes some potentially breaking changes in how the e
34
34
35
35
Additionally, Sentry has deprecated sending events to the `/api/{project_id}/store` endpoint in favor of a new `/api/{project_id}/envelope` endpoint (and a new structure for the body of the post requests). Again, if you self-host an older version of the Sentry service, sending events to the `store` endpoint might be your only option. There is a new module setting, `sentryEventEndpoint`, that defaults to `store`, but can be set to `envelope` to enable sending events to the modern endpoint.
36
36
37
+
In version 2, `cookie` and `form` scope data will not be sent with events by default. To enable sending this data, use the new `sendCookies` and `sendPostData` settings.
38
+
37
39
## CFML App Installation
38
40
39
41
If your app uses neither ColdBox nor LogBox, you can still instantiate the `SentryService` and use it directly so long as you prep it with the settings it needs.
@@ -142,6 +144,10 @@ settings = {
142
144
enableExceptionLogging :true,
143
145
// Send messages to Sentry in a thread
144
146
async :true,
147
+
// Whether to include client cookies when sending request information to Sentry
148
+
sendCookies :false,
149
+
// Whether to include POST data (e.g. FORM) when sending request information to Sentry
150
+
sendPostData :false,
145
151
// Don't sent URL or FORM field values of these names to Sentry
0 commit comments