[Koha-bugs] [Bug 23068] Add ability for Koha to handle X-Forwarded-For headers so REMOTE_ADDR features work behind a proxy

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23068

--- Comment #53 from David Cook <dcook at prosentient.com.au> ---
(In reply to David Cook from comment #52)
> I can get the client IP via $ENV{REMOTE_ADDR} in Koha as set by
> Koha::Middleware::RealIP, but plack.log is still using the proxy address as
> set by Plack::Middleware::ReverseProxy. (I've confirmed that by hacking on
> Plack::Middleware::ReverseProxy.pm in k-t-d.)

This one is driving me a little crazy...

It looks like /usr/share/perl5/Plack/Runner.pm applies the
Plack::Middleware::AccessLog middleware and that's wrapped around the app
last...

Yet it appears to be getting the REMOTE_ADDR from
Plack::Middleware::ReverseProxy and not Koha::Middleware::RealIP. (If you
remove Plack::Middleware::ReverseProxy then it'll get it from
Koha::Middleware::RealIP.)

But it seems more complicated than that because adding Koha::Middleware::RealIP
*after* Plack::Middleware::ReverseProxy doesn't seem to make a difference which
seems illogical...

-- 
You are receiving this mail because:
You are watching all bug changes.