Chris Dent d3352ff422 Identify the keystone service when raising 503 ... When the keystonemiddleware is used directly in the WSGI stack of an application, the 503 that is raised when the keystone service errors or cannot be reached needs to identify that keystone is the service that has failed, otherwise it appears to the client that it is the service they are trying to access is down, which is misleading. This addresses the problem in the most straightforward way possible: the exception that causes the 503 is given a message including the word "Keystone". The call method in BaseAuthTokenTestCase gains an expected_body_string kwarg. If not None, the response body (as a six.text_type) is compared with the value. Change-Id: Idf211e7bc99139744af232f5ea3ecb4be41551ca Closes-Bug: #1747655 Closes-Bug: #1749797		2018-02-20 17:32:41 +01:00
..
_common	Replace six.iteritems() with .items()	2017-07-12 13:43:55 +07:00
audit	Update URLs in documentation	2017-07-20 16:38:16 +08:00
auth_token	Identify the keystone service when raising 503	2018-02-20 17:32:41 +01:00
echo	Replace six.iteritems() with .items()	2017-07-12 13:43:55 +07:00
locale	Imported Translations from Zanata	2017-11-16 06:38:15 +00:00
tests	Identify the keystone service when raising 503	2018-02-20 17:32:41 +01:00
__init__.py	Moving middleware to new location	2014-06-19 15:50:41 -07:00
ec2_token.py	use oslo.log instead of logging	2017-01-13 03:24:18 +00:00
exceptions.py	Create a Config object	2016-06-10 18:21:56 +00:00
fixture.py	Remove use of positional decorator	2017-08-07 13:18:19 -07:00
i18n.py	Update URLs in documentation	2017-07-20 16:38:16 +08:00
opts.py	Move auth token opts calculation into auth_token	2016-06-13 14:03:23 -03:00
s3_token.py	Rename auth_uri to www_authenticate_uri	2017-10-11 14:00:49 +02:00