33
edits
Difference between revisions of "Tech pages/XEP-0368"
Jump to navigation
Jump to search
no edit summary
| Line 42: | Line 42: | ||
Another (incorrectly named) example can be found at the [https://wiki.debian.org/InstallingProsody#XMPP_over_HTTPS Debian Wiki] | Another (incorrectly named) example can be found at the [https://wiki.debian.org/InstallingProsody#XMPP_over_HTTPS Debian Wiki] | ||
You then need to setup your [https://wiki.xmpp.org/web/SRV_Records SRV Records] so clients can find it, personally I have mine set up like so (for a JID like me@example.org): | |||
_xmpps-client._tcp.example.org. 86400 IN SRV 5 0 443 xmpp.example.org. | |||
_xmpp-client._tcp.example.org. 86400 IN SRV 10 0 443 xmpp.example.org. | |||
_xmpp-client._tcp.example.org. 86400 IN SRV 15 0 5222 xmpp.example.org. | |||
This prioritizes XEP-0368 TLS over port 443 first, then plain XMPP over 443 next, and lastly plain XMPP over 5222. A client that doesn't support XEP-0368 just skips the first record. | |||
Please note the target can be anything, example.org, xmpp.example.org, or some.unrelated.domain.net, just as long as it's listening on those ports and has a valid certificate for example.org in this case. | |||