From 1f6515cec460a5f93d875d565f23d3b907d6ad4e Mon Sep 17 00:00:00 2001 From: melissaml <ma.lei@99cloud.net> Date: Tue, 27 Feb 2018 12:03:48 +0800 Subject: [PATCH] Update the invalid url for swift page Change-Id: I2e2c158d0a785f9198fa2050aee0ecd25bdd92f4 --- doc/source/index.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/source/index.rst b/doc/source/index.rst index d0d10c3..dca14e1 100644 --- a/doc/source/index.rst +++ b/doc/source/index.rst @@ -26,7 +26,7 @@ Before discussing how to install Swauth within a Swift system, it might help to 2. It intercepts requests to ``/auth/`` (by default). -3. It also uses Swift's `authorize callback <https://docs.openstack.org/developer/swift/development_auth.html>`_ and `acl callback <https://docs.openstack.org/developer/swift/misc.html#module-swift.common.middleware.acl>`_ features to authorize Swift requests. +3. It also uses Swift's `authorize callback <https://docs.openstack.org/swift/latest/development_auth.html>`_ and `acl callback <https://docs.openstack.org/swift/latest/misc.html#acls>`_ features to authorize Swift requests. 4. Swauth will also make various internal calls to the Swift WSGI pipeline it's installed in to manipulate containers and objects within an ``AUTH_.auth`` (by default) Swift account. These containers and objects are what store account and user information.