[Koha-bugs] [Bug 25361] Support X-Forwarded-* headers

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Thu Aug 6 03:00:17 CEST 2020


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

--- Comment #6 from David Cook <dcook at prosentient.com.au> ---
(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 reported this one, so I'm not 100% sure of my
original intent. I didn't word it very well.

However, in Koha, we actually only use X-Forwarded-For and X-Forwarded-Proto.
Bug 23068 explicitly uses X-Forwarded-For, while X-Forwarded-Proto is used by
Plack::Middleware::ReverseProxy to set $ENV->{HTTPS} to true.

Apache's mod_proxy_http automatically sets X-Forwarded-For, X-Forwarded-Host,
and X-Forwarded-Server, I believe, but doesn't do others like X-Forwarded-Proto
(which is why Tomas added it in Bug 21267). 

AWS load balancers pass X-Forwarded-For, X-Forwarded-Proto, and
X-Forwarded-Port. 

I mostly see utility for X-Forwarded-For and X-Forwarded-Proto. Not really sure
why a person would care about X-Forwarded-Port 

I think I'll close this one for now.

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


More information about the Koha-bugs mailing list