File

spec/scansion/server_contact_info.scs @ 13651:b9d369f77121

prosodyctl: Further deprecate start/stop/restart commands when installed Despite the warning we introduced, many people continue to try using prosodyctl to manage Prosody in the presence of systemctl (e.g. #1688). Also, despite the warning, prosodyctl proceeded with the operation. This means the commands could be invoked by accident, and cause a situation that is hard to recover from (needing to manually track down stray processes). This commit disables all the problematic commands by default, but this can still be overridden using --force or via a config option. We only perform this check when we believe Prosody has been "installed" for system-wide use (i.e. running it from a source directory is still supported).
author Matthew Wild <mwild1@gmail.com>
date Thu, 06 Feb 2025 14:51:31 +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