Software /
code /
prosody
File
spec/scansion/basic_roster.scs @ 12481:2ee27587fec7
net: refactor sslconfig to not depend on LuaSec
This now requires that the network backend exposes a tls_builder
function, which essentially wraps the former util.sslconfig.new()
function, passing a factory to create the eventual SSL context.
That allows a net.server backend to pick whatever it likes as SSL
context factory, as long as it understands the config table passed by
the SSL config builder. Heck, a backend could even mock and replace the
entire SSL config builder API.
author | Jonas Schäfer <jonas@wielicki.name> |
---|---|
date | Sat, 02 Apr 2022 11:15:33 +0200 |
parent | 9305:f14c81fd44a4 |
line wrap: on
line source
# Basic roster test [Client] Romeo jid: user@localhost password: password [Client] Juliet jid: juliet@localhost password: password --------- Romeo connects Juliet connects Romeo sends: <presence/> Romeo receives: <presence from="${Romeo's full JID}" /> Romeo sends: <iq type="get" id="roster1"> <query xmlns='jabber:iq:roster'/> </iq> Romeo receives: <iq type="result" id="roster1"> <query ver='{scansion:any}' xmlns="jabber:iq:roster"/> </iq> # Add nurse to roster Romeo sends: <iq type="set" id="roster2"> <query xmlns="jabber:iq:roster"> <item jid='nurse@localhost'/> </query> </iq> # Receive the roster add result Romeo receives: <iq type="result" id="roster2"/> # Receive the roster push Romeo receives: <iq type="set" id="{scansion:any}"> <query xmlns='jabber:iq:roster' ver='{scansion:any}'> <item jid='nurse@localhost' subscription='none'/> </query> </iq> Romeo sends: <iq type="result" id="fixme"/> # Fetch the roster, it should include nurse now Romeo sends: <iq type="get" id="roster3"> <query xmlns='jabber:iq:roster'/> </iq> Romeo receives: <iq type="result" id="roster3"> <query xmlns='jabber:iq:roster' ver="{scansion:any}"> <item subscription='none' jid='nurse@localhost'/> </query> </iq> Romeo disconnects