<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 16px; font-family: Calibri, sans-serif;">
<div>Hello,</div>
<div><br>
</div>
<div>I am looking for advice on an interesting case a customer of our swift cluster has come with. </div>
<div><br>
</div>
<div>They have uploaded a large object (~5G) to a swift container "containerA". Swift broke this object into segments, creating a container for those segments "containerA_segments".</div>
<div>If both containers are set to public, this object can be downloaded.</div>
<div><br>
</div>
<div>They want this container to be private and only serve up content to a specific refer domain.</div>
<div>So, they set the following ACL on "containerA" ".r:<secret-key>.example.com,.rlistings</div>
<div>Where the secret-key is one their proxy re-directs requests to.</div>
<div><br>
</div>
<div>Now, they can not get the object in containerA. </div>
<div>Setting "containerA_segments" to the same ACL as containerA also does not work.</div>
<div><br>
</div>
<div>We have found that the only way to access this object is to set the ACL on "containerA_segments" to public.</div>
<div>This isn't desirable because it means the segments container is now public even though containerA is private.</div>
<div><br>
</div>
<div>Is this expected?</div>
<div><br>
</div>
<div>-Adam</div>
<br>
<hr>
<font face="Arial" color="Gray" size="1"><br>
This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to
which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may
be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.<br>
</font>
</body>
</html>