prosody
5059a639f61e
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 @ 12545:5059a639f61e

util.watchdog: Update to use "new" util.timer API When this module was written, it wasn't possible to cancel or reschedule a timer. Times have changed, and we should take advantage of those new methods. This module becomes a very thin wrapper around util.timer now, but I'd argue it's still a very common and useful concept/abstraction to have around. Possible API change: this removes the 'last_reset' field of the watchdog. This was never really intended as a public thing, and I can't find any code that uses it, so I consider removal to be safe.
author Matthew Wild <mwild1@gmail.com>
date Sat, 11 Jun 2022 21:11:01 +0100
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