From 8ed6e663d5f9827c2cd4928a54b02d2fa244af6c Mon Sep 17 00:00:00 2001
From: Tim Burke <tim.burke@gmail.com>
Date: Thu, 31 Aug 2017 23:36:38 +0000
Subject: [PATCH] Stop clearing req.acl in DLO

This has been pure misdirection since DLO was pulled out of the proxy
server; req.acl is always set by the object controller before calling
swift.authorize.

See TestDlo.test_dlo_referer_on_segment_container in
test/functional/test_dlo.py for proof that we still enforce segment
container ACLs properly.

Change-Id: I5321b5537787fcea126065243f1c4bd5e601181e
Related-Change: Ib3b3830c246816dd549fc74be98b4bc651e7bace
---
 swift/common/middleware/dlo.py | 2 --
 1 file changed, 2 deletions(-)

diff --git a/swift/common/middleware/dlo.py b/swift/common/middleware/dlo.py
index 4aa6c8e12b..e7bb3feb5d 100644
--- a/swift/common/middleware/dlo.py
+++ b/swift/common/middleware/dlo.py
@@ -232,8 +232,6 @@ class GetContext(WSGIContext):
         container = unquote(container)
         obj_prefix = unquote(obj_prefix)
 
-        # manifest might point to a different container
-        req.acl = None
         version, account, _junk = req.split_path(2, 3, True)
         error_response, segments = self._get_container_listing(
             req, version, account, container, obj_prefix)