Does the notification widget for React support WS service on a path?
I'm deploying the self-hosted version to my infrastructure and have put API and WS services on a path in the same domain eg:
I see lots of websocket requests. But they are all to
wss://testing.something.io/socket.io/?EIO=4&transport=websocket
Is that correct?
Do I need to a) host the widget myself or b) move WS service to be on it's own sub-domain and remove the path?
I also get CORS errors in Chrome, for now I've disabled CORS in Chrome to remove this issue. But feels like I'm missing some config to allow localhost while in development.
I see lots of websocket requests. But they are all to
wss://testing.something.io/socket.io/?EIO=4&transport=websocket
Is that correct?
Do I need to a) host the widget myself or b) move WS service to be on it's own sub-domain and remove the path?
I also get CORS errors in Chrome, for now I've disabled CORS in Chrome to remove this issue. But feels like I'm missing some config to allow localhost while in development.
