Swift supports and/or implements a number of authentication schemes
including tempauth, Keystone, tempurl, formpost and container sync. In
this fix, we use a catch-all, "Swift". The realm is the account (where
known) or "unknown" (bad path or where the 401 is returned from code
that does not have the request). Examples:
Www-Authenticate: Swift realm="AUTH_1234567889" Www-Authenticate: Swift realm="unknown"
Reviewed: https:/ /review. openstack. org/43476 github. com/openstack/ swift/commit/ 9807a358c6d1314 d25e3a41da75be5 851fa0ac27
Committed: http://
Submitter: Jenkins
Branch: master
commit 9807a358c6d1314 d25e3a41da75be5 851fa0ac27
Author: Donagh McCabe <email address hidden>
Date: Fri Aug 23 15:03:08 2013 +0100
Add WWW-Authenticate to 401 responses
Per http:// www.ietf. org/rfc/ rfc2616. txt, when a 401 error is returned, the Authenticate response header MUST also be returned. The format is www.ietf. org/rfc/ rfc2617. txt.
Www-
described in http://
Swift supports and/or implements a number of authentication schemes
including tempauth, Keystone, tempurl, formpost and container sync. In
this fix, we use a catch-all, "Swift". The realm is the account (where
known) or "unknown" (bad path or where the 401 is returned from code
that does not have the request). Examples:
Fixes bug #1215491
Change-Id: I03362789318dfa 156d3733ef93487 95062a9cfc4