Software /
code /
prosody
File
tools/migration/migrator.cfg.lua @ 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 | 12168:33e856c65033 |
child | 13295:b788307ca06a |
line wrap: on
line source
local data_path = "../../data"; local vhost = { "accounts", "account_details", "roster", "vcard", "private", "blocklist", "privacy", "archive-archive", "offline-archive", "pubsub_nodes-pubsub", "pep-pubsub", } local muc = { "persistent", "config", "state", "muc_log-archive", }; input { hosts = { ["example.com"] = vhost; ["conference.example.com"] = muc; }; type = "internal"; path = data_path; } output { type = "sql"; driver = "SQLite3"; database = data_path.."/prosody.sqlite"; } --[[ input { type = "internal"; path = data_path; } output { type = "sql"; driver = "SQLite3"; database = data_path.."/prosody.sqlite"; } ]]