https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25361
David Cook changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25361
--- Comment #6 from David Cook ---
(In reply to Marcel de Rooy from comment #5)
> I do not understand what this report is about. We already have support for
> X-Forwarded headers. So what is the point ?
It's been a while since I
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25361
Marcel de Rooy changed:
What|Removed |Added
CC||m.de.r...@rijksmuseum.nl
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25361
--- Comment #4 from David Cook ---
Plack:
- Apache should set X-Forwarded-* headers so that they can be consumed by
Plack::Middleware::ReverseProxy
CGI:
- Apache should set HTTP headers using X-Forwarded-* headers from a separate
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25361
--- Comment #3 from David Cook ---
Thanks to https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21267, the
X-Forwarded-Proto header gets set in Apache when using Plack, so
Plack::Middleware::ReverseProxy will set the
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25361
David Cook changed:
What|Removed |Added
See Also||https://bugs.koha-community
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25361
--- Comment #2 from David Cook ---
(In reply to David Cook from comment #1)
> Actually, looking at
> https://github.com/plack/Plack/wiki/How-to-detect-reverse-proxy-and-SSL-
> frontend and
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25361
--- Comment #1 from David Cook ---
Actually, looking at
https://github.com/plack/Plack/wiki/How-to-detect-reverse-proxy-and-SSL-frontend
and https://metacpan.org/pod/Plack::Middleware::ReverseProxy, it looks like
Plack-enabled Koha
