Imagine we have a load balancer accepting *https* connections only and talking to solum-api via *http*. The LB typically talks to solum-api using 'Host' and 'X-Forwarded-Proto' headers as following:
$ curl -H "x-auth-token: `cat ~/local_token`" -H "host: load.balancer.com" -H "X-Forwarded-Proto: https" -i http://10.0.2.15:9777/v1/
HTTP/1.0 200 OK
Date: Thu, 21 Aug 2014 03:33:21 GMT
Server: WSGIServer/0.1 Python/2.7.3
Content-Length: 513
Content-Type: application/json; charset=UTF-8
{"name": "solum", "services_uri": "http://load.balancer.com/v1/services", "components_uri": "http://load.balancer.com/v1/components", "uri": "http://load.balancer.com/v1", "language_packs_uri": "http://load.balancer.com/v1/language_packs", "extensions_uri": "http://load.balancer.com/v1/extensions", "implementation_version": "2014.1.0", "assemblies_uri": "http://load.balancer.com/v1/assemblies", "type": "platform", "plans_uri": "http://load.balancer.com/v1/plans", "description": "solum native implementation"}
So solum handles "Host" header correctly but ignores "X-Forwarded-Proto", so we only see *http* in the response body above, but we expect *https* in this case, i.e. "https://load.balancer.com/v1/services" for services endpoint.
For reference, Heat has fixed a similar issue:
https:/