File

mod_http: Limit unencrypted http port (5280) to loopback by default Since accessing this port directly over the wider Internet is unlikely to intentional anymore. Most uses will likely be by reverse proxies, by mistake or because of trouble configuring HTTPS. Blocking mistaken uses is just a good thing, letting users send potentially private things unencrypted tends to be Strongly Discouraged these days. Many reverse proxy setups operate over loopback, so listening there instead of all interfaces is a net improvement. Improved automatic certificate location and SNI support has mostly eliminated the need for manual certificate configuration so HTTPS should Just Work once certificates have been provided. For local testing during development, connecting over loopback is likely fine as well. When really needed, `http_interfaces` can still be set. Suggested by Link Mauve

# XEP-0092: Software Version / mod_version

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

-----

Romeo connects

Romeo sends:
	<iq id='lx2' to='localhost' type='get'>
		<query xmlns='jabber:iq:version'/>
	</iq>

# Version string would vary so we can't do an exact match atm
# Inclusion of <os/> is disabled in the config, it should be absent
Romeo receives:
	<iq id='lx2' from='localhost' type='result'>
		<query xmlns='jabber:iq:version' scansion:strict='true'>
			<name>Prosody</name>
			<version scansion:strict='false'/>
		</query>
	</iq>


Romeo disconnects