File

spec/scansion/mam_prefs_prep.scs @ 13127:f45a29b32f7a

mod_http: Make RFC 7239 Forwarded opt-in for now to be safe Supporting both methods at the same time may open to spoofing attacks, whereby a client sends a Forwarded header that is not stripped by a reverse proxy, leading Prosody to use that instead of the X-Forwarded-* headers actually sent by the proxy. By only supporting one at a time, it can be configured to match what the proxy uses. Disabled by default since implementations are sparse and X-Forwarded-* are everywhere.
author Kim Alvefur <zash@zash.se>
date Sat, 03 Jun 2023 21:53:20 +0200
parent 11727:f3aee8a825cc
line wrap: on
line source

# mod_mam should apply JIDprep in prefs

[Client] Romeo
	jid: romeo@localhost
	password: password

-----

Romeo connects

Romeo sends:
	<iq id="lx2" type="set">
		<prefs xmlns="urn:xmpp:mam:2" default="roster">
			<always>
				<jid>JULIET@MONTAGUE.LIT</jid>
			</always>
			<never>
				<jid>MONTAGUE@MONTAGUE.LIT</jid>
			</never>
		</prefs>
	</iq>

Romeo receives:
	<iq id="lx2" type="result">
		<prefs xmlns="urn:xmpp:mam:2" default="roster">
			<always>
				<jid>juliet@montague.lit</jid>
			</always>
			<never>
				<jid>montague@montague.lit</jid>
			</never>
		</prefs>
	</iq>

Romeo disconnects