The original reason that www-authenticate returns a catch-all "swift" response is that the auth_uri parameter is not available to keystoneauth. The proxy-server.conf file looks like::
[filter:keystoneauth]
use = egg:swift#keystoneauth
It might seem a trivial change to move the auth_uri to the [default] section or to make a copy in [filter:keystoneauth]. However, that requires action by deployers....so your proposed patch is not backward compatible.
The original reason that www-authenticate returns a catch-all "swift" response is that the auth_uri parameter is not available to keystoneauth. The proxy-server.conf file looks like::
[filter: auth_token] /identity- endpoint/ v2.0
...
auth_uri = https:/
...
[filter: keystoneauth] keystoneauth
use = egg:swift#
It might seem a trivial change to move the auth_uri to the [default] section or to make a copy in [filter: keystoneauth] . However, that requires action by deployers....so your proposed patch is not backward compatible.