-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
User mandatory in DSN #184
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
Comments
How are you using Sentry without the public key? |
I am not using Sentry, only RavenJS. |
Oh, interesting. So coming up soon, we're going to be supporting pluggable transports, and I think this would just be resolved by your own transport. Ideally, raven-js would be geared for working with Sentry out of the box then if you want to do something different, your transport would have that flexibility. See: #183 |
No, is nothing very complex, HTTP/HTTPS. |
Right, I understand. My point is that I don't want it to work like that out of the box because that will affect all Sentry users. By having a separate transport, you'd be able to plug in one that was dumber than ours that didn't need to send along the auth stuff, for example. |
This was resolved with #361 |
v1.1.8
works: 'https://zuzu@localhost/LoggerSite/logging/0'
doesn't: 'https://localhost/LoggerSite/logging/0'
and I need the second.
Thank you
The text was updated successfully, but these errors were encountered: