tempurl uses wrong HMAC with full path
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-swiftclient |
Fix Released
|
Medium
|
Christian Schwede |
Bug Description
It's easy to get an invalid tempurl from the swiftclient
# if you use the full uri for a resource
vagrant@saio:~$ swift tempurl GET 30 http://
http://
# you get an invalid tempurl (no error/warning to flag invalid input!?)
vagrant@saio:~$ curl "http://
401 Unauthorized: Temp URL invalid
# it expects you to use just the path
vagrant@saio:~$ swift tempurl GET 30 /v1/AUTH_
/v1/AUTH_
# which works
vagrant@saio:~$ curl "http://
awesome
.. but it should detect the difference and do the right thing in both cases.
A similar issue was reported/discovered in swift's own `swift-temp-url` lp bug #1607519
In progress: https:/ /review. openstack. org/#/c/ 357063/