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
// Suggested Configuration:{host: {client: "my.website.com",server: "0.0.0.0"},https: true,port:{client: false,// number or falseserver: 8081}}
For Features; What is the motivation and/or use-case for the feature?
This would allow users who have a proxy configuration set up to allow the default port 443 for wss:// connections to work as intended. The issue I'm having is that the address the websocket tries to listen over is wss://my.website.com:8081 which means I have to set my nginx server running on docker to also listen to port 8081 as well as 443. The ideal way this would work for me would be that the client just tries to connect to wss://my.website.com without any port information added. Then it would route correctly through 443
Code
For Features; What is the motivation and/or use-case for the feature?
This would allow users who have a proxy configuration set up to allow the default port 443 for wss:// connections to work as intended. The issue I'm having is that the address the websocket tries to listen over is
wss://my.website.com:8081which means I have to set my nginx server running on docker to also listen to port 8081 as well as 443. The ideal way this would work for me would be that the client just tries to connect towss://my.website.comwithout any port information added. Then it would route correctly through 443