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
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.
The text was updated successfully, but these errors were encountered:
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:
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
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:
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.
The text was updated successfully, but these errors were encountered: