Keystone v3 header shouldn't be distinguished by case
Bug #1553398 reported by
Fernando Ribeiro
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
zaqar |
New
|
Undecided
|
Unassigned |
Bug Description
The 'X-Project-Id' (lower case 'd') header of Keystone v3 [1] is distinguished by case in several places in Zaqar, including the WebSocket endpoint, which generate errors if the 'X-Project-ID' (upper case 'D') header is sent instead.
You may refer to section 3.2 of RFC 7230 [1] for details.
summary: |
- Misspelled Keystone header + Misspelled Keystone v3 header |
description: | updated |
Changed in zaqar: | |
assignee: | nobody → Tin Lam (tl3438) |
Changed in zaqar: | |
status: | New → In Progress |
summary: |
- Misspelled Keystone v3 header + Keystone v3 Header Shouldn't be Distinguished by Case |
summary: |
- Keystone v3 Header Shouldn't be Distinguished by Case + Keystone v3 header shouldn't be distinguished by case |
Changed in zaqar: | |
status: | In Progress → New |
assignee: | Tin Lam (tl3438) → nobody |
description: | updated |
To post a comment you must log in.
Per review comment - https:/ /review. openstack. org/#/c/ 288809/ - not sure if the fix is needed, since header is in fact case insensitive. Might be just code churn to lower case the D.