prosody
5b0c8e499288
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 @ 12254:5b0c8e499288

modulemanager: Add plugin load filter that reads module metadata from source Metadata in modules is added using lines formatted as: --% key: value Where key is a valid identifier string, and value is also a string (leading and trailing whitespace are trimmed during parsing). The initial supported keys are: --% requires_core_features: feature1, feature2, ... --% conflicts_core_features: feature1, feature2. ... These 'features' map to features reported by the new core.features module. A benefit of this load-time metadata approach compared to e.g. something like module:requires()/module:conflicts() is that we can continue to look in module search paths for a suitable module. Aborting an already-loaded module due to a version conflict would be too late.
author Matthew Wild <mwild1@gmail.com>
date Fri, 04 Feb 2022 14:20:00 +0000
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