Get Container ACL
Get Container ACL operation gets the permissions for the specified container. The permissions indicate whether container data may be accessed publicly.
As of version 2009-09-19, the container permissions provide the following options for managing container access:
Full public read access: Container and blob data can be read via anonymous request. Clients can enumerate blobs within the container via anonymous request, but they can't enumerate containers within the storage account.
Public read access for blobs only: Blob data within this container can be read via anonymous request, but container data isn't available. Clients can't enumerate blobs within the container via anonymous request.
No public read access: Container and blob data can be read by the account owner only.
Get Container ACL also returns details about any container-level access policies that are specified on the container that may be used with shared access signatures. For more information, see Define a stored access policy.
All public access to the container is anonymous, as is access via a shared access signature.
Get Container ACL request may be constructed as follows. We recommend that you use HTTPS. Replace myaccount with the name of your storage account:
|Method||Request URI||HTTP version|
Emulated storage service request
When you're making a request against the emulated storage service, specify the emulator hostname and Blob Storage port as
127.0.0.1:10000, followed by the emulated storage account name:
|Method||Request URI||HTTP version|
For more information, see Use the Azurite emulator for local Azure Storage development.
The following additional parameters may be specified on the request URI:
Request error codes
The required and optional request headers are described in the following table:
||Required. Specifies the authorization scheme, account name, and signature. For more information, see Authorize requests to Azure Storage.|
||Required. Specifies the Coordinated Universal Time (UTC) for the request. For more information, see Authorize requests to Azure Storage.|
||Optional, version 2012-02-12 and later. If it's specified,
||Required for all authorized requests. Specifies the version of the operation to use for this request. For more information, see Versioning for the Azure Storage services.|
||Optional. Provides a client-generated, opaque value with a 1-kibibyte (KiB) character limit that's recorded in the logs when logging is configured. We highly recommend that you use this header to correlate client-side activities with requests that the server receives. For more information, see Monitor Azure Blob Storage.|
The response includes an HTTP status code, a set of response headers, and a response body.
A successful operation returns status code 200 (OK).
For information about status codes, see Status and error codes.
Response error codes
The response for this operation includes the following headers. The response may also include additional standard HTTP headers. All standard headers conform to the HTTP/1.1 protocol specification.
||Indicates whether data in the container may be accessed publicly and the level of access. Possible values include:
If this header isn't returned in the response, the container is private to the account owner.
||The entity tag for the container. If the request version is 2011-08-18 or later, the ETag value is enclosed in quotation marks.|
||Returns the date and time when the container was last modified. The date format follows RFC 1123. For more information, see Represent date/time values in error codes.
Any operation that modifies the container or its properties or metadata updates the last modified time. Operations on blobs don't affect the last modified time of the container.
||Uniquely identifies the request that was made, and it can be used to troubleshoot the request. For more information, see Troubleshoot API operations.|
||Indicates the service version that was used to execute the request. This header is returned for requests that were made against version 2009-09-19 and later.|
||A UTC date/time value that's generated by the service, which indicates the time when the response was initiated.|
||Can be used to troubleshoot requests and their corresponding responses. The value of this header is equal to the value of the
If a container-level access policy has been specified for the container,
Get Container ACL returns the signed identifier and access policy in the response body.
<?xml version="1.0" encoding="utf-8"?> <SignedIdentifiers> <SignedIdentifier> <Id>unique-value</Id> <AccessPolicy> <Start>start-time</Start> <Expiry>expiry-time</Expiry> <Permission>abbreviated-permission-list</Permission> </AccessPolicy> </SignedIdentifier> </SignedIdentifiers>
Response Status: HTTP/1.1 200 OK Response Headers: Transfer-Encoding: chunked x-ms-blob-public-access: container Date: Sun, 25 Sep 2011 20:28:22 GMT ETag: "0x8CAFB82EFF70C46" Last-Modified: Sun, 25 Sep 2011 19:42:18 GMT x-ms-version: 2011-08-18 Server: Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0 <?xml version="1.0" encoding="utf-8"?> <SignedIdentifiers> <SignedIdentifier> <Id>MTIzNDU2Nzg5MDEyMzQ1Njc4OTAxMjM0NTY3ODkwMTI=</Id> <AccessPolicy> <Start>2009-09-28T08:49:37.0000000Z</Start> <Expiry>2009-09-29T08:49:37.0000000Z</Expiry> <Permission>rwd</Permission> </AccessPolicy> </SignedIdentifier> </SignedIdentifiers>
Get Container ACL operation only supports Shared Key authorization.
Only the account owner may read data in a particular storage account, unless the account owner has specified that blobs within the container are available for public read access, or has made resources in the container available via a shared access signature.
Restrict access to containers and blobs
Define a stored access policy
Set Container ACL
Authorize requests to Azure Storage
Status and error codes
Blob Storage error codes