Environment is Sense 3.0.1.
I am trying to get http header authentication working with Google Chrome, using a Chrome extension for injecting the needed auth header. Quite convenient way of handling authentication during development.
This works flawlessly in Firefox, but when injecting the same headers using Chrome (have tried 5-6 different Chrome extensions for header manipulation), the Sense Hub loads fine, but when opening the app I sometimes get a "not connected" error dialog, and sometimes a "listener must be a function" dialog.
Somehow the Sense client does not play nice with Chrome's way of injecting headers, or vice versa. Which is kind of weird, http headers have been around for ages, and I would expect them to work consistently across browsers.
Anyone else that have run into this?