I was able to reproduce it.
Warning message needs to update in this case. Also, a valid looking URI should not be generated if object or container does not exist. Instead, tempURL should be discarded.
#in below case, object does not exist. still it generates a valid URI.
ubuntu@saio-experiment:~/swift$ swift-temp-url GET 3600 /v1/AUTH_test/test_container/file4.txt secrete_key_b
/v1/AUTH_test/test_container/file4.txt?temp_url_sig=a7b362cbb3a5c3482b1cc26ee84a1741de5f3c9d&temp_url_expires=1469742082
#in below case, container and object does not exist. still it generates a valid URI.
ubuntu@saio-experiment:~/swift$ swift-temp-url GET 3600 /v1/AUTH_test/test_container1/file4.txt secrete_key_b
/v1/AUTH_test/test_container1/file4.txt?temp_url_sig=6cffe72513448d2de0b31700fb71427b727e3628&temp_url_expires=1469742091
I was able to reproduce it.
Warning message needs to update in this case. Also, a valid looking URI should not be generated if object or container does not exist. Instead, tempURL should be discarded.
#in below case, object does not exist. still it generates a valid URI. saio-experiment :~/swift$ swift-temp-url GET 3600 /v1/AUTH_ test/test_ container/ file4.txt secrete_key_b test/test_ container/ file4.txt? temp_url_ sig=a7b362cbb3a 5c3482b1cc26ee8 4a1741de5f3c9d& temp_url_ expires= 1469742082
ubuntu@
/v1/AUTH_
#in below case, container and object does not exist. still it generates a valid URI. saio-experiment :~/swift$ swift-temp-url GET 3600 /v1/AUTH_ test/test_ container1/ file4.txt secrete_key_b test/test_ container1/ file4.txt? temp_url_ sig=6cffe725134 48d2de0b31700fb 71427b727e3628& temp_url_ expires= 1469742091
ubuntu@
/v1/AUTH_