prosody
4c8941b5b05e
spec/scansion/muc_mediated_invite.scs

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

Software / code / prosody

File

spec/scansion/muc_mediated_invite.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 9291:329a670ae975
line wrap: on
line source

# MUC: Mediated invites

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

[Client] Juliet
	jid: user2@localhost
	password: password

-----

Romeo connects

Romeo sends:
	<presence to="room@conference.localhost/Romeo">
		<x xmlns="http://jabber.org/protocol/muc"/>
	</presence>

Romeo receives:
	<presence from='room@conference.localhost/Romeo'>
		<x xmlns='http://jabber.org/protocol/muc#user'>
			<status code='201'/>
			<item jid="${Romeo's full JID}" affiliation='owner' role='moderator'/>
			<status code='110'/>
		</x>
	</presence>

Romeo receives:
	<message type='groupchat' from='room@conference.localhost'><subject/></message>

# Submit config form
Romeo sends:
	<iq id='config1' to='room@conference.localhost' type='set'>
		<query xmlns='http://jabber.org/protocol/muc#owner'>
			<x xmlns='jabber:x:data' type='submit'>
				<field var='FORM_TYPE'>
					<value>http://jabber.org/protocol/muc#roomconfig</value>
				</field>
			</x>
		</query>
	</iq>

Romeo receives:
	<iq id="config1" from="room@conference.localhost" type="result">
	</iq>

# Juliet connects
Juliet connects

Juliet sends:
	<presence/>

Juliet receives:
	<presence/>


# Romeo invites Juliet to join the room

Romeo sends:
	<message to="room@conference.localhost" id="invite1">
		<x xmlns="http://jabber.org/protocol/muc#user">
			<invite to="${Juliet's JID}" />
		</x>
	</message>

Juliet receives:
	<message from="room@conference.localhost" id="invite1">
		<x xmlns="http://jabber.org/protocol/muc#user">
			<invite from="room@conference.localhost/Romeo">
				<reason/>
			</invite>
		</x>
		<body>room@conference.localhost/Romeo invited you to the room room@conference.localhost</body>
		<x xmlns="jabber:x:conference" jid="room@conference.localhost"/>
	</message>