Re: Azure Blob strange request sequence

瀏覽次數:3 次
跳到第一則未讀訊息

Adrian Cole

未讀,
2013年4月17日 晚上7:41:122013/4/17
收件者:jcl...@googlegroups.com、jclou...@googlegroups.com
The reason is that when ACL support was made available, not all BlobStores supported blob-level acls.  In fact CloudFiles didn't support it at all.  For this reason, to support public acls, we made a flag at container level.  As ACL metadata doesn't usually come back in headers, this implies looking up a container ACL lazy as you are noticing.

Years have passed.  Swift now supports ACLs, so we can do object-level for blobstores (including hpcloud and swift, which currently emulate public ACLs via CDN).  Moreover, we could allow for disabling of ACL lookup.

So, that is the history, and this moving away from that would be a nice one for when we enter the incubator.. nudge nudge :)


-A


On Wed, Apr 17, 2013 at 4:30 PM, Rustam Aliyev <rustam...@code.az> wrote:
After digging a bit in the code I found where ACLs are checked from:

https://github.com/jclouds/jclouds/blob/master/providers/azureblob/src/main/java/org/jclouds/azureblob/blobstore/functions/BlobPropertiesToBlobMetadata.java#L66

...
BlobPropertiesToBlobMetadata.apply(BlobProperties) line: 66
AzureBlobToBlob.apply(AzureBlob) line: 49
AzureBlobStore.getBlob(String, String, GetOptions) line: 180
AzureBlobStore(BaseBlobStore).getBlob(String, String) line: 183
...

Does it mean that jclouds checks container ACL and applies it to blob (in case if not private) after each GET? I'm not sure I understand reason for that. Can someone explain?

-
Rustam.


On 16/04/2013 01:34, Rustam Aliyev wrote:
Hi,

I'm using Azure Blob through proxy and when fetching blob I see 2 requests:

1. GET /container/blob   --> Blob contents
2. GET /container?restype=container&comp=acl    -> Container ACL

First request is successfully passed by proxy and correct response received 200 + body.
The problem is that authentication for the second request (ACL) fails. I can see that all required parameters are passed by proxy.

In any case, does anyone know why jclouds retreives container metadata after retreiving blob? In the code I'm only doing putBlob(...).


Many thanks,
Rustam.

--
You received this message because you are subscribed to the Google Groups "jclouds" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jclouds+unsubscribe@googlegroups.com.
To post to this group, send email to jcl...@googlegroups.com.
Visit this group at http://groups.google.com/group/jclouds?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.



回覆所有人
回覆作者
轉寄
0 則新訊息