Actions
Bug #7957
closedRegression in Wt 4.5.0: behind-reverse-proxy doesn't work right with dedicated process mode anymore
Start date:
01/05/2021
Due date:
% Done:
100%
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.
Updated by Roel Standaert almost 4 years ago
- Status changed from InProgress to Implemented @Emweb
Updated by Roel Standaert almost 4 years ago
- Status changed from Implemented @Emweb to Resolved
Updated by Roel Standaert about 3 years ago
- Status changed from Resolved to Closed
Actions