aboutsummaryrefslogtreecommitdiffstats
path: root/prosodyctl
diff options
context:
space:
mode:
authorKim Alvefur <zash@zash.se>2022-01-15 15:13:41 +0100
committerKim Alvefur <zash@zash.se>2022-01-15 15:13:41 +0100
commitb1874898028aa584bb02c3ec082ab8c9f54ae951 (patch)
tree0ebba5aad0f674f33d43843c7cb3b777a1c27b9e /prosodyctl
parente0e180aa9d9cac1e427ac23be49aca0c4059f755 (diff)
downloadprosody-b1874898028aa584bb02c3ec082ab8c9f54ae951.tar.gz
prosody-b1874898028aa584bb02c3ec082ab8c9f54ae951.zip
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
Diffstat (limited to 'prosodyctl')
0 files changed, 0 insertions, 0 deletions