prosody
4c8941b5b05e
spec/scansion/server_contact_info.scs

Find changesets by keywords by author, files, the commit message, revision number or hash, or revset expression.

Software / code / prosody

File

spec/scansion/server_contact_info.scs @ 12586:4c8941b5b05e 0.12

core.s2smanager: Don't remove unrelated session on close of bidi session Normally with bidi, any outgoing connection should be the same as the incoming, hence when closing a bidi connection it should be removed as a route to the remote server. However it is not guaranteed, a remote bidi-capable server might have decided to open a new connection for some reason. This can lead to a situation where there are two bidi connections, and the s2sout route is a locally initiated s2sout connection. In this case, such a s2sout connection should be kept. Noticed in a rare case where bidi has just been enabled on a running server, and something establishes new connections immediately when a connection is closed.
author Kim Alvefur <zash@zash.se>
date Mon, 27 Jun 2022 01:22:36 +0200
parent 11583:4ee7a6a8753e
line wrap: on
line source

# XEP-0157: Contact Addresses for XMPP Services
# mod_server_contact_info

[Client] Romeo
	jid: romeo@localhost
	password: password

-----

Romeo connects

Romeo sends:
	<iq type='get' id='lx2' to='localhost'>
		<query xmlns='http://jabber.org/protocol/disco#info'/>
	</iq>

# Ignore other disco#info features, identities etc

Romeo receives:
	<iq from='localhost' id='lx2' type='result'>
		<query xmlns='http://jabber.org/protocol/disco#info' scansion:strict='false'>
			<x xmlns='jabber:x:data' type='result'>
				<field type='hidden' var='FORM_TYPE'>
					<value>http://jabber.org/network/serverinfo</value>
				</field>
				<field type='list-multi' var='abuse-addresses'>
					<value>mailto:abuse@localhost</value>
					<value>xmpp:abuse@localhost</value>
				</field>
				<field type='list-multi' var='admin-addresses'>
					<value>mailto:admin@localhost</value>
					<value>xmpp:admin@localhost</value>
				</field>
				<field type='list-multi' var='feedback-addresses'>
					<value>http://localhost/feedback.html</value>
					<value>mailto:feedback@localhost</value>
					<value>xmpp:feedback@localhost</value>
				</field>
				<field type='list-multi' var='sales-addresses'>
					<value>xmpp:sales@localhost</value>
				</field>
				<field type='list-multi' var='security-addresses'>
					<value>xmpp:security@localhost</value>
				</field>
				<field type='list-multi' var='status-addresses'>
					<value>gopher://status.localhost</value>
				</field>
				<field type='list-multi' var='support-addresses'>
					<value>https://localhost/support.html</value>
					<value>xmpp:support@localhost</value>
				</field>
			</x>
		</query>
	</iq>


Romeo sends:
	<iq type='get' id='lx2' to='conference.localhost'>
		<query xmlns='http://jabber.org/protocol/disco#info'/>
	</iq>

	<iq from='localhost' id='lx2' type='result'>
		<query xmlns='http://jabber.org/protocol/disco#info' scansion:strict='false'>
			<x xmlns='jabber:x:data' type='result'>
				<field type='hidden' var='FORM_TYPE'>
					<value>http://jabber.org/network/serverinfo</value>
				</field>
				<field type='list-multi' var='abuse-addresses'/>
				<field type='list-multi' var='admin-addresses'>
					<value>xmpp:admin@localhost</value>
				</field>
				<field type='list-multi' var='feedback-addresses'/>
				<field type='list-multi' var='sales-addresses'/>
				<field type='list-multi' var='security-addresses'/>
				<field type='list-multi' var='status-addresses'/>
				<field type='list-multi' var='support-addresses'/>
			</x>
		</query>
	</iq>

Romeo disconnects