Liberty behind proxy

Many load balancers / reverse proxies implement a defacto-standard set of headers which tells the backend server in question that a request was forwarded through a proxy and gives additional indications on original protocol.

A Reverse Proxy commonly adds these headers:

X-Forwarded-For: [true client-ip]
X-Forwarded-Proto: [usually https, http, wss or ws]
X-Forwarded-Port: [the port of the reverse proxy exposed to the client, mostly 80 or 443]
X-Forwarded-Host: [the original hostname the client requested]

... in some cases, a reverse proxy may send an alternative form ...

Forwarded: for=[true client-ip],proto=[usually https, http, wss or ws],host=[original hostname]:[original port]

From this information Libetry should be able to correctly come to the following:

1.) See that it is running behind a reverse proxy.
2.) See that the connection may or not be secure by checking the invocation scheme (making httpsIndicatorHeader redundant).
3.) How to correctly generate self-referencing links.

In the context of this I believe only the httpsIndicatorHeader-attribute is made redundant by taking into account these de-facto-standard headers, the httpsRedirectProxy-flag which was mentioned in the original request is likely not made redundant by this, because sometimes the server must know beforehand how to form a secure or insecure redirect-URL.