Bug 21477

Summary: Use of REMOTE_ADDR causes problems when Koha is behind a proxy
Product: Koha Reporter: Nick Clemens <nick>
Component: Architecture, internals, and plumbingAssignee: Kyle M Hall <kyle>
Status: RESOLVED DUPLICATE QA Contact: Testopia <testopia>
Severity: normal    
Priority: P5 - low CC: 1joynelson, ephetteplace, eveal, mtj
Version: master   
Hardware: All   
OS: All   
See Also: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14407
Change sponsored?: --- Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:

Description Nick Clemens 2018-10-02 17:25:59 UTC
For sysprefs like: RestrictedPageLocalIP we check the REMOTE_ADDR to get the IP, for setups behind a proxy we have seen issues as the IP is not matching the users IP.

We should have a support for checking X_FORWARDED_FOR in order to check the IP of the end user
Comment 1 Eric Phetteplace 2018-10-15 16:04:26 UTC
I just wanted to chime in that this effects us, as we'd like to offer limited access to media via the Restricted Page feature without forcing a sign-in from on campus but are hosted behind a proxy by ByWater.
Comment 2 Ed Veal 2019-05-28 20:52:48 UTC
I would also like to add that we would be interested in a solution to this issue as well. It is preventing us from providing the best customer service we can as a library. 

Ed
Comment 3 Kyle M Hall 2019-06-13 17:21:52 UTC

*** This bug has been marked as a duplicate of bug 23068 ***