Comment 8 for bug 1472295

I think this is actually working as designed. I would view comment 2 as the fix for a misconfiguration (i.e. user error) issue, not a workaround. Per the description, the clients are calling keystone's GET https://<ip>:5000/v2.0 and yet the response they get back from keystone wrongly shows http instead of https. If they get bad information from keystone, it's harsh to blame the clients...