swiftclient /info call does not respect --insecure

[clayg]

If you have a cluster with a self signed cert you can't make a `swift info` request against it - you get:

[Errno 1] _ssl.c:504: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed

using --insecure or SWIFTCLIENT_INSECURE=true works fine for *other* requests - but these options are not respected for the info command - and they should be!

Note: if you curl https://myswiftcluster/info with -k it works fine, it's not the cluster or something specific about that endpoint - it's just the command line tool.

[Pete Zaitcev (zaitcev)]

Unfortunately it's supposed to work like described. The explicit flag is necessary. In that way "swift --insecure" is an equivalent of "curl -k".

[Pete Zaitcev (zaitcev)]

Oh, wait, never mind. Are you saying that --insecure has no effect on /info although it should?

[clayg (clay-gerrard)]

correct, I tried to clean up the wording - please feel free to amend further.

[Pete Zaitcev (zaitcev)]

Very low fruit indeed, see:
  https://review.openstack.org/129364