Versions links are wrong when behind a proxy changing path

Bug #1843586 reported by Pierre Riteau
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

When behind a proxy changing the path to the Blazar API, the links returned in the versions response are incorrect. This is the case with the default DevStack configuration which uses the ProxyPass directive.

$ http GET X-Auth-Token:$OS_AUTH_TOKEN
HTTP/1.1 300 Multiple Choices
Connection: close
Content-Type: application/json
Date: Wed, 11 Sep 2019 12:52:13 GMT
Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips mod_wsgi/3.4 Python/2.7.5
Transfer-Encoding: chunked

    "versions": [
            "id": "v1.0",
            "links": [
                    "href": "",
                    "rel": "self"
            "max_version": "1.0",
            "min_version": "1.0",
            "status": "CURRENT"
            "id": "v2.0",
            "links": [
                    "href": "",
                    "rel": "self"
            "status": "DEPRECATED"

The links should be to and

Keystone and Glance both have a `public_endpoint` configuration value which they use to build the correct URL.

Revision history for this message
Pierre Riteau (priteau) wrote :

Check if this could be fixed with:

enable_proxy_headers_parsing = True

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.