After switching to https service, a problem occurred in the WebSocket communication part.

WEB TMS WEB Core
1

After switching to https service, a problem occurred in the WebSocket communication part.

In the Amazon (IaaS as Windows) cloud, four servers are in service:
1. DB server (with MSSQL)
2. ApiServer (to TMS XData)
3. Web Server (Apache)
4.EventServer(WebSockets)

Amazon ELB is set up as an https service and is running without problems.
However, communication with the LocalWebSocketServer and work pages running on each work PC is failing.
When communicating with LocalWebSocketServer among https services in the TMS Web Core project, it would be nice to have a way to connect WebSocket (ws:..) in the http environment.
Request a review response.

3

Hi,

This is a browser limitation. There's nothing we can do to change that, you simply cannot connect to an insecure (ws://) WebSocket server from a secure context as the browser blocks that for security reasons.

If there is no way for you to bring the WebSocket server to wss:// then you'll need to individually set each browser to allow insecure content. This is however not recommended to do.