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

Improve error handling when can't communicate with service(s) #65

Open
alechenninger opened this issue Mar 25, 2015 · 2 comments
Open
Labels

Comments

@alechenninger
Copy link
Contributor

Currently if you try to talk to a lightblue host that you can't, say you don't have a cert that you need, you'll get this in your browser's console. For example, Chrome says this:

Failed to load resource: net::ERR_BAD_SSL_CLIENT_AUTH_CERT

This is ALL you get though, and the UI does nothing to tell you about this. So the UI could be nice and inform you about these kinds of errors.

@derek63
Copy link
Member

derek63 commented Mar 26, 2015

It would also be nice to have a friendly error message for the next error we encountered if you have a valid cert, but the server is misconfigured for CORS support:

[Error] XMLHttpRequest cannot load https://lightbluedevserver.example.com/rest/metadata. Origin https://lightbluedevserver.example.com is not allowed by Access-Control-Allow-Origin. (data, line 0)

@alechenninger
Copy link
Contributor Author

Waiting on #89 to use angular-ui-bootstrap alert for these

@alechenninger alechenninger changed the title Data management: Improve error handling when can't communicate with service(s) Improve error handling when can't communicate with service(s) Jul 14, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants