wss protocol problem

[nabillefi]

Initially, I used a ws address to integrate a project with my Vue application, which worked correctly. However, when I deployed the frontend code to the cloud, the WebSocket was blocked by the browser because it required the protocol to be wss. To overcome this issue, I added ingress to convert the protocol from http to https. Since then, I have been able to successfully receive messages through the WebSocket. Do you have any suggestions for a potential solution?

[salsferrazza]

This appears to be expected behavior because I don't believe one can mix modes between secure and insecure. Meaning, if the initial handshake request is done over http(s), then the socket connection itself must also be over http(s).

In the first case (presuming you were running locally), both were running over HTTP. The cloud deployment of the web front-end likely enforces HTTPS, which trickles down into what is expected from the websocket connection.

Is there a particular reason (other than overhead) to refrain from running sockets over HTTPS?