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

User mandatory in DSN #184

Closed
devel-pa opened this issue Jan 23, 2014 · 6 comments
Closed

User mandatory in DSN #184

devel-pa opened this issue Jan 23, 2014 · 6 comments
Milestone

Comments

@devel-pa
Copy link

v1.1.8
works: 'https://zuzu@localhost/LoggerSite/logging/0'
doesn't: 'https://localhost/LoggerSite/logging/0'
and I need the second.
Thank you

@mattrobenolt
Copy link
Contributor

How are you using Sentry without the public key?

@devel-pa
Copy link
Author

I am not using Sentry, only RavenJS.

@mattrobenolt
Copy link
Contributor

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

@devel-pa
Copy link
Author

No, is nothing very complex, HTTP/HTTPS.
I need a regular log of the JS errors from the browser in a text file, near the rest of the server error.

@mattrobenolt
Copy link
Contributor

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.

@mattrobenolt mattrobenolt added this to the 1.2 milestone Feb 16, 2014
@mattrobenolt
Copy link
Contributor

This was resolved with #361

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

No branches or pull requests

2 participants