api microversion header should conform to new guidlines
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Undecided
|
Scott DAngelo |
Bug Description
As outlined in this api-wg spec:
https:/
microversion headers should be of the form:
OpenStack-
i.e OpenStack-
Two extra headers are always returned in the response::
OpenStack-
Vary: OpenStack-
And:
note: Servers must be prepared to deal with multiple
OpenStack-
designed to address multiple services always sends the headers it
thinks it needs. Most Python frameworks will handle this by setting
the value of the header to the values of all matching headers,
joined by a ',' (comma). For example ``compute 2.11,identity
2.114``.
Changed in cinder: | |
assignee: | nobody → Scott DAngelo (scott-dangelo) |
Changed in cinder: | |
status: | New → In Progress |
Reviewed: https:/ /review. openstack. org/286901 /git.openstack. org/cgit/ openstack/ cinder/ commit/ ?id=ef7ed8dcb28 e743edbd839261a 948fa84089f8fa
Committed: https:/
Submitter: Jenkins
Branch: master
commit ef7ed8dcb28e743 edbd839261a948f a84089f8fa
Author: scottda <email address hidden>
Date: Tue Mar 1 14:42:05 2016 -0700
support new HTTP microversion header
According to API working group guidelines: /review. openstack. org/#/c/ 243414
https:/
microversion headers should be of the form: API-Version: [SERVICE_TYPE] 2.114
OpenStack-
i.e OpenStack- API-Version: volume 3.22
Two extra headers are always returned in the response:
Vary: OpenStack-
note: Servers must be prepared to deal with multiple -API-Version headers. This could happen when a client
OpenStack
designed to address multiple services always sends the headers it
thinks it needs. Most Python frameworks will handle this by setting
the value of the header to the values of all matching headers,
joined by a ',' (comma). For example ``compute 2.11,identity
2.114``.
Closes-Bug: #1551941 41e3b551dd98276 06c2e013511
Change-Id: I658e54966c390b