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: 13126:d043834f15d2
child: 13188:96df571b5941
--- a/CHANGES	Sat Jun 03 17:10:04 2023 +0200
+++ b/CHANGES	Sat Jun 03 21:53:20 2023 +0200
@@ -42,7 +42,7 @@
 - mod_blocklist: New option 'migrate_legacy_blocking' to disable migration from mod_privacy
 - Ability to use SQLite3 storage using LuaSQLite3 instead of LuaDBI
 - Moved all modules into the Lua namespace `prosody.`
-- Forwarded header from RFC 7239 supported
+- Forwarded header from RFC 7239 supported, disabled by default
 
 ## Removed