Can not specify which port / address needs to be used when redirecting http -> https about configurable-http-proxy HOT 3 CLOSED

I don't think this is related to #1289 because unlike the Hub, CHP never specifies from internal configuration what ip anyone should connect to.

CHP doesn't use the bind address (which is ~always 0.0.0.0) for this, it uses the Host header so that it should be the same as the connect ip for a properly assembled request. My guess is the upstream proxy is not passing through the Host header. We could try to figure out what the proxied Host was (e.g. X-Forwarded-Host), or we could require that the upstream proxy preserve host headers for this feature.

Can you inspect the headers to see what kubernetes is passing?

If there is an additional upstream proxy, it probably makes more sense for it to do the HTTP->HTTPS redirect, anyway.

from configurable-http-proxy.

I think, IIUC, the problem is less about the host, and more about the port?
Inside the k8s cluster, the HTTPS service is listening on 8443 and the HTTP service on 8000. These are portforwarded on the loadbalancer from 443 and 80 respectively.
When --port 8443 and --redirect-port 8000 are set, then a user trying to connect to :80 is portforwarded to :8000 which is 301'd to :8443, which doesn't work.
It may need an option like --redirect-to 443 which would be used on https://github.com/jupyterhub/configurable-http-proxy/blob/master/bin/configurable-http-proxy#L349 to that port (rather than the listen.port)

from configurable-http-proxy.

closed by #187

from configurable-http-proxy.