4b0c953f7f
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
7 lines
316 B
Plaintext
7 lines
316 B
Plaintext
---
|
|
fixes:
|
|
- |
|
|
When manila API is run behind a proxy webserver, the API service was
|
|
parsing the major API version requested incorrectly, leading to incorrect
|
|
responses. This behavior has now been fixed. See `launchpad bug 1818081
|
|
<https://bugs.launchpad.net/manila/+bug/1818081>`_ for more details. |