commit 5a3be01535d3902e1ee21ca070d4918adefc2018
Author: Goutham Pacha Ravi <email address hidden>
Date: Wed Mar 13 16:50:27 2019 -0700
Fix API version inferred w/ un-versioned URLs
With [1], we fixed the issue with v1 API URLs when
configuring manila with a reverse proxy, like uwsgi.
However, the version discovery can be made against a
"unversioned" URL, i.e, the "/" endpoint.
Example version discovery target when there's no reverse
proxy:
curl -i -X GET www.openstack-overcloud.com:8786/
Example version discovery target when manila is configured
with a web proxy:
curl -i -X GET www.openstack-overcloud.com/shared-file-system/
Currently, the API assumes that a v2 endpoint is requested
and hence sets a default API version in the request, which
results in the wrong headers communicated to the client.
Fix this issue. The release note added with [1] should
suffice for this fix.
[1] I0363d7174f3d7ddefa8ced59b182faed665e9c36
Change-Id: I50d1024ee8485b8290c24fa850e60755b518fff3
Closes-Bug: #1818081
(Cherry-picked from commit 4b0c953f7fe7afbbbece8db7edce8efe69fb4387)
Reviewed: https:/ /review. openstack. org/643431 /git.openstack. org/cgit/ openstack/ manila/ commit/ ?id=5a3be01535d 3902e1ee21ca070 d4918adefc2018
Committed: https:/
Submitter: Zuul
Branch: stable/rocky
commit 5a3be01535d3902 e1ee21ca070d491 8adefc2018
Author: Goutham Pacha Ravi <email address hidden>
Date: Wed Mar 13 16:50:27 2019 -0700
Fix API version inferred w/ un-versioned URLs
With [1], we fixed the issue with v1 API URLs when
configuring manila with a reverse proxy, like uwsgi.
However, the version discovery can be made against a
"unversioned" URL, i.e, the "/" endpoint.
Example version discovery target when there's no reverse
proxy:
curl -i -X GET www.openstack- overcloud. com:8786/
Example version discovery target when manila is configured
with a web proxy:
curl -i -X GET www.openstack- overcloud. com/shared- file-system/
Currently, the API assumes that a v2 endpoint is requested
and hence sets a default API version in the request, which
results in the wrong headers communicated to the client.
Fix this issue. The release note added with [1] should
suffice for this fix.
[1] I0363d7174f3d7d defa8ced59b182f aed665e9c36 8290c24fa850e60 755b518fff3 bbece8db7edce8e fe69fb4387)
Change-Id: I50d1024ee8485b
Closes-Bug: #1818081
(Cherry-picked from commit 4b0c953f7fe7afb