Raven.js: configure() lets DSN be exposed in page source?

1

Hi all,

I am new to Sentry, and just trying to set up Raven.js to track Javascript errors today.

And I notice my Sentry DSN got exposed to public because of applying the function mentioned in the documentation used to install Raven.js on my website:

Raven.config('MY DSN').install()

I reckon DSN should be private, otherwise, I guess others can maliciously use it and trigger Javascript errors? If so, may I ask how I can prevent this?
Thanks in advance.

2

The DSN can be public. I replied to another topic here which asked the same question: JS - how avoid anyone mess with my log?