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

No 'to' attribute:
	IQ:			Pass to appropriate handler
	Presence:		Broadcast to contacts
				- if initial presence, also send out presence probes
					- if probe would be to local user, generate presence stanza for them
	Message:		Route as if it is addressed to the bare JID of the sender

To a local host:
	IQ:			Pass to appropriate handler
	Presence:		-
	Message:		Deliver to admin?

To local contact:
	Bare JID:
		IQ:		Pass to appropriate handler
		Presence:	Broadcast to all resources
		Message:	Route to 'best' resource
	Full JID:
		IQ:		Send to resource
		Presence:	Send to resource
		Message:	Send to resource
	Full JID but resource not connected:
		IQ:		Return service-unavailable
		Message:	Handle same as if to bare JID
		Presence:	Drop (unless type=subscribe[ed])

To remote contact:
	Initiate s2s connection if necessary
	Send stanza across