Archive Docker image: Provide ENVs for HTTPS/SSL with a Reverse Proxy

[gunterze]

Provide ENVs for HTTPS/SSL with a Reverse Proxy:

HTTP_PROXY_ADDRESS_FORWARDING

If this is enabled then the X-Forwarded-For and X-Forwarded-Proto headers will be used to determine the peer address.
This allows applications that are behind a proxy to see the real address of the client, rather than the address
of the proxy. (optional, default is false).

REDIRECT_HTTPS_PORT

HTTPS port to redirect requests that require security too. (optional, default is 8443).
Have to be set different to HTTPS_PORT, if running behind a HTTPS/SSL reverse proxy listing on a different port.

[petrkalina]

Only effective for http listener, not https currently!

[petrkalina]

seems HTTP_PROXY_ADDRESS_FORWARDING=true renders WILDFLY_RESOLVE_PEER_ADDRESS=true ineffective. Surprisingly, it becomes effective with adding a logging filter i.e. vua jboss-cli script:

batch
/subsystem=undertow/configuration=filter/custom-filter=request-logging-filter:add(class-name=io.undertow.server.handlers.RequestDumpingHandler, module=io.undertow.core)
/subsystem=undertow/server=default-server/host=default-host/filter-ref=request-logging-filter:add
run-batch

[gunterze]

dcm4che-dockerfiles/dcm4chee-arc-psql@4f763a7
dcm4che-dockerfiles/dcm4chee-arc-psql@1c7bd86
dcm4che-dockerfiles/dcm4chee-arc-psql@dab0933