| 2016-03-04 22:51:51 |
Fernando Ribeiro |
bug |
|
|
added bug |
| 2016-03-04 22:52:09 |
Fernando Ribeiro |
summary |
Misspelled Keystone header |
Misspelled Keystone v3 header |
|
| 2016-03-04 22:52:17 |
Fernando Ribeiro |
description |
The 'X-Project-Id' header of the Keystone v3 API [1] is misspelled as 'X-Project-ID' in several places in Zaqar.
[1] http://specs.openstack.org/openstack/keystone-specs/api/v3/identity-api-v3.html#headers |
The 'X-Project-Id' header of Keystone v3 [1] is misspelled as 'X-Project-ID' in several places in Zaqar.
[1] http://specs.openstack.org/openstack/keystone-specs/api/v3/identity-api-v3.html#headers |
|
| 2016-03-05 00:09:49 |
Tin Lam |
zaqar: assignee |
|
Tin Lam (tl3438) |
|
| 2016-03-05 00:19:44 |
Tin Lam |
zaqar: status |
New |
In Progress |
|
| 2016-03-08 11:38:30 |
Fernando Ribeiro |
summary |
Misspelled Keystone v3 header |
Keystone v3 Header Shouldn't be Distinguished by Case |
|
| 2016-03-08 11:45:33 |
Fernando Ribeiro |
description |
The 'X-Project-Id' header of Keystone v3 [1] is misspelled as 'X-Project-ID' in several places in Zaqar.
[1] http://specs.openstack.org/openstack/keystone-specs/api/v3/identity-api-v3.html#headers |
The 'X-Project-Id' (lower case 'd') header of Keystone v3 [1] is distinguished by case in several places in Zaqar, including the HTTP and WebSocket endpoints, 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.
[1] https://tools.ietf.org/html/rfc7230 |
|
| 2016-03-08 13:05:12 |
Fernando Ribeiro |
summary |
Keystone v3 Header Shouldn't be Distinguished by Case |
Keystone v3 header shouldn't be distinguished by case |
|
| 2016-03-09 21:50:48 |
Fernando Ribeiro |
zaqar: status |
In Progress |
New |
|
| 2016-03-09 21:51:07 |
Fernando Ribeiro |
zaqar: assignee |
Tin Lam (tl3438) |
|
|
| 2016-03-26 02:09:34 |
Fernando Ribeiro |
description |
The 'X-Project-Id' (lower case 'd') header of Keystone v3 [1] is distinguished by case in several places in Zaqar, including the HTTP and WebSocket endpoints, 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.
[1] https://tools.ietf.org/html/rfc7230 |
The 'X-Project-Id' (lower case 'd') header of Keystone v3 [1] is distinguished by case in several places in Zaqar, including the WSGI and WebSocket endpoints, 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.
[1] https://tools.ietf.org/html/rfc7230 |
|
| 2016-04-05 17:45:40 |
Fernando Ribeiro |
description |
The 'X-Project-Id' (lower case 'd') header of Keystone v3 [1] is distinguished by case in several places in Zaqar, including the WSGI and WebSocket endpoints, 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.
[1] https://tools.ietf.org/html/rfc7230 |
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.
[1] https://tools.ietf.org/html/rfc7230 |
|
