Get Queue ACL
Get Queue ACL operation returns details about any stored access policies specified on the queue that may be used with Shared Access Signatures. For more information, see Define a stored access policy.
Get Queue ACL operation is available in version 2012-02-12 and newer.
Get Queue ACL request may be constructed as follows. HTTPS is recommended. Replace myaccount with the name of your storage account:
|Method||Request URI||HTTP Version|
Emulated storage service URI
When making a request against the emulated storage service, specify the emulator hostname and Queue service port as
127.0.0.1:10001, followed by the emulated storage account name:
|Method||Request URI||HTTP Version|
For more information, see Differences Between the Storage Emulator and Azure Storage Services.
The following additional parameters may be specified on the request URI.
The following table describes required and optional request headers.
||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.|
||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 KiB character limit that is recorded in the analytics logs when storage analytics logging is enabled. Using this header is highly recommended for correlating client-side activities with requests received by the server. For more information, see About Storage Analytics Logging and Azure Logging: Using Logs to Track Storage Requests.|
The response includes an HTTP status code, a set of response headers, and a response body.
A successful operation returns status code
For information about status codes, see Status and 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.
||This header uniquely identifies the request that was made and can be used for troubleshooting the request. For more information, see Troubleshooting API Operations.|
||Indicates the version of the Queue service used to execute the request. This header is returned for requests made against version 2009-09-19 and later.|
||A UTC date/time value generated by the service that indicates the time at which the response was initiated.|
||This header can be used to troubleshoot requests and corresponding responses. The value of this header is equal to the value of the
If a stored access policy has been specified for the queue,
Get Queue 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 Date: Sun, 10 Jun 2012 20:28:22 GMT x-ms-version: 2012-02-12 Server: Windows-Azure-Queue/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>raup</Permission> </AccessPolicy> </SignedIdentifier> </SignedIdentifiers>
Only the account owner may call this operation.
Only the account owner may read queue data in a particular storage account, unless the account owner has made resources in the queue available via a Shared Access Signature.