keystone cli --debug does not report inbound wire traffic
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-keystoneclient |
Fix Released
|
Wishlist
|
Gal Vinograd |
Bug Description
Steps to reproduce:
keystone --debug service-list
Expected:
Full wire trace of inbound and outbound traffic.
Actual:
$ keystone --debug service-list
connect: (192.168.2.10, 5000)
send: 'POST /v2.0/tokens HTTP/1.1\r\nHost: 192.168.
reply: 'HTTP/1.1 200 OK\r\n'
header: Content-Type: application/json; charset=UTF-8
header: Content-Length: 2000
header: Date: Wed, 15 Feb 2012 18:04:54 GMT
connect: (192.168.2.10, 35357)
send: u'GET /v2.0/OS-
reply: 'HTTP/1.1 200 OK\r\n'
header: Content-Type: application/json; charset=UTF-8
header: Content-Length: 503
header: Date: Wed, 15 Feb 2012 18:04:54 GMT
+------
| id | name | type | description |
+------
| 3ca61c10aa21485
| 3e95ca6222fc421
| ca0f96a9ecef4a6
| ea4ec4a6f02d470
+------
Changed in keystone: | |
status: | New → Triaged |
affects: | keystone → python-keystoneclient |
Changed in python-keystoneclient: | |
assignee: | nobody → Gal Vinograd (gal-vinograd) |
Is that just missing the content bodies of the reply, or is there something else you're looking for?