Software /
code /
prosody
Annotate
doc/stanza_routing.txt @ 12686:5f182bccf33f
mod_component: Require 'from' attribute on stanzas by default
The old behaviour of falling back to the component domain when it is missing
has been merged into the logic for the existing "validate_from_addresses"
option (which is strict by default).
ejabberd already rejects component stanzas with no 'from' (as the XEP
requires), and this has led to compatibility issues for components that were
seemingly working fine with Prosody.
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Sun, 28 Aug 2022 07:51:50 +0100 |
parent | 22:2856dfc1f5cc |
rev | line source |
---|---|
12 | 1 No 'to' attribute: |
2 IQ: Pass to appropriate handler | |
3 Presence: Broadcast to contacts | |
4 - if initial presence, also send out presence probes | |
5 - if probe would be to local user, generate presence stanza for them | |
6 Message: Route as if it is addressed to the bare JID of the sender | |
7 | |
8 To a local host: | |
9 IQ: Pass to appropriate handler | |
10 Presence: - | |
11 Message: Deliver to admin? | |
12 | |
13 To local contact: | |
14 Bare JID: | |
15 IQ: Pass to appropriate handler | |
16 Presence: Broadcast to all resources | |
17 Message: Route to 'best' resource | |
18 Full JID: | |
19 IQ: Send to resource | |
20 Presence: Send to resource | |
21 Message: Send to resource | |
21 | 22 Full JID but resource not connected: |
23 IQ: Return service-unavailable | |
24 Message: Handle same as if to bare JID | |
25 Presence: Drop (unless type=subscribe[ed]) | |
12 | 26 |
27 To remote contact: | |
28 Initiate s2s connection if necessary | |
29 Send stanza across | |
22
2856dfc1f5cc
Various documentation updates, and added names.txt :)
Matthew Wild <mwild1@gmail.com>
parents:
21
diff
changeset
|
30 |