File

spec/scansion/keep_full_sub_req.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 10515:35bf3b80480f
line wrap: on
line source

# server MUST keep a record of the complete presence stanza comprising the subscription request (#689)

[Client] Alice
	jid: pars-a@localhost
	password: password

[Client] Bob
	jid: pars-b@localhost
	password: password

[Client] Bob's phone
	jid: pars-b@localhost/phone
	password: password

---------

Alice connects

Alice sends:
	<presence to="${Bob's JID}" type="subscribe">
		<preauth xmlns="urn:xmpp:pars:0" token="1tMFqYDdKhfe2pwp" />
	</presence>

Alice disconnects

Bob connects

Bob sends:
	<presence/>

Bob receives:
	<presence from="${Bob's full JID}"/>

Bob receives:
	<presence from="${Alice's JID}" type="subscribe">
		<preauth xmlns="urn:xmpp:pars:0" token="1tMFqYDdKhfe2pwp" />
	</presence>

Bob disconnects

# Works if they reconnect too

Bob's phone connects

Bob's phone sends:
	<presence/>

Bob's phone receives:
	<presence from="${Bob's phone's full JID}"/>


Bob's phone receives:
	<presence from="${Alice's JID}" type="subscribe">
		<preauth xmlns="urn:xmpp:pars:0" token="1tMFqYDdKhfe2pwp" />
	</presence>

Bob's phone disconnects