Project

General

Profile

Bug #7957

Regression in Wt 4.5.0: behind-reverse-proxy doesn't work right with dedicated process mode anymore

Added by Roel Standaert 17 days ago. Updated 8 days ago.

Status:
Resolved
Priority:
Normal
Target version:
Start date:
01/05/2021
Due date:
% Done:

0%

Estimated time:

Description

The child processes will disable behind reverse proxy and set 127.0.0.1 and ::1 as trusted proxies.

However, the parent process merely adds extra proxies to the X-Forwarded-For header. Any trusted proxies herein should still be considered trusted proxies by the child process.

The fix is to leave the behind reverse proxy option alone (the old behavior), and add 127.0.0.1 and ::1 to the existing list of reverse proxies.

#1

Updated by Roel Standaert 17 days ago

  • Target version set to 4.5.1
#2

Updated by Roel Standaert 16 days ago

  • Status changed from InProgress to Implemented @Emweb
#3

Updated by Roel Standaert 8 days ago

  • Status changed from Implemented @Emweb to Resolved

Also available in: Atom PDF