Mercurial > prosody-modules
view mod_compat_dialback/README.markdown @ 4326:f6fdefc5c6ac
mod_roster_command: Fix subscription when the "user JID" is a bare domain.
Do not attempt to update the roster when the user is bare domain (e.g. a
component), since they don't have rosters and the attempt results in an error:
$ prosodyctl mod_roster_command subscribe proxy.example.com contact@example.com
xxxxxxxxxxFailed to execute command: Error: /usr/lib/prosody/core/rostermanager.lua:104: attempt to concatenate local 'username' (a nil value)
stack traceback:
/usr/lib/prosody/core/rostermanager.lua:104: in function 'load_roster'
/usr/lib/prosody/core/rostermanager.lua:305: in function 'set_contact_pending_out'
mod_roster_command.lua:44: in function 'subscribe'
| author | Boris Grozev <boris@jitsi.org> |
|---|---|
| date | Tue, 05 Jan 2021 13:15:00 -0600 |
| parents | 41ebdb331b94 |
| children |
line wrap: on
line source
--- summary: Workaround for Dialback with some servers that violate RFC 6120 ... This module provides a workaround for servers that do not set the `to` attribute on stream headers, which is required per [RFC6120]: > ## 4.7.2. to > > For initial stream headers in both client-to-server and > server-to-server communication, the initiating entity MUST include the > 'to' attribute and MUST set its value to a domainpart that the > initiating entity knows or expects the receiving entity to service. As a side effect of [this issue](https://prosody.im/issues/issue/285), Prosody 0.10 will be unable to do [Dialback][xep220] with servers that don't follow this. # Known servers affected * Openfire 3.10.2 (and probably earlier versions)