Hi, > wss://<xmpp-service-name>:5443/ws > ws://<xmpp-service-name>:5443/ws > wss://<xmpp-service-name>/ws > ws://<xmpp-service-name>/ws
- ws://...:5443/ws makes no sense. Port 5443 is obviously a reference to HTTPS 443 port which is TLS encrypted, so you shouldn't make non-TLS connections to 5443. If any, use something like port 5080 or 5280. - While technically you could do starttls over unencrypted websockets to get an encrypted connection, most clients probably won't do this and for browsers that's incredibly hard to implement. Non-TLS connections shouldn't be supported at all. So I'd opt for not providing implicit unencrypted wss endpoints at all. - Same as Sam, I'd also opt to use a path that is specific to XMPP and not as generic as /ws - at least for the default port variant. Best would probably be to register and use a well-known URI, e.g. /.well-known/xmpp-websocket. - The reason for the XEP seems to be to ease deployments and not require XEP-0156 because that relies on modifying the HTTPS server running on <xmpp-service-name>:443. Yet the wss://<xmpp-service-name>/ws endpoint would have exactly the same requirement and complexity to set up. Marvin On 03.02.21 01:28, Jonas Schäfer (XSF Editor) wrote: > The XMPP Extensions Editor has received a proposal for a new XEP. > > Title: Implicit XMPP WebSocket Endpoints > Abstract: > This document specifies implicit connection endpoints for XMPP over > WebSocket (RFC 7395). > > URL: https://xmpp.org/extensions/inbox/xep-iwe.html > > The Council will decide in the next two weeks whether to accept this > proposal as an official XEP. > _______________________________________________ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: [email protected] > _______________________________________________ > _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
