Mercurial > prosody-modules
view mod_compat_dialback/README.markdown @ 4249:64aa1d9d70ac
mod_rest: Catch and log errors in callback promise chain
From the code it looks like it should be possible to reply to an error
stanza, but it did not. Turns out I was saved by my local developer mode
module which throws errors if an attempt is made to create an errror
reply to an error stanza. However nothing collects this error from the
promise, so all I got was confusion.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Sun, 15 Nov 2020 16:25:49 +0100 |
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)