The 2009-09-19 version of Azure Storage includes these changes:
Enhancements to Shared Key authorization. For more information, see Authorize requests to Azure Storage.
The introduction of a new type of blob, the page blob, which is optimized for random read/write operations. With a page blob, you can write to a range of bytes in a blob. For more information, see Understand block blobs, append blobs, and page blobs.
New naming rules for container, blob, and queue metadata. For more information, see Name and reference containers, blobs, and metadata and Name queues and metadata.
Blob snapshots, which are read-only versions of a blob as it existed at the time the snapshot was taken. For more information, see HTTP operations on Blob Storage resources and the Snapshot Blob operation.
Blob leases, which ensure a one-minute exclusive write lock on a blob. For more information, see the Lease Blob operation.
Enhanced control over publicly accessible container and blob resources. For more information, see Restrict access to containers and blobs.
Anonymous access to the root container. For more information, see Work with the root container.
x-ms-versionresponse header, returned by all API operations. This header indicates which version of the API was used to make the request.
Additional options for enumerating containers, blobs, and queues. With these options, you can return metadata in the enumeration and, in the case of blobs, return snapshots and uncommitted blobs in the list. For more information, see the List Containers, List Blobs, and List Queues operations.
Additional blob properties, which save values that are specified for standard HTTP headers. For more information, see the Set Blob Properties operation.
A requirement that REST calls to Azure Table Storage include the
MaxDataServiceVersionheaders on every request.
New values are returned in the
Serverresponse header to identify the service that handled the request. These values are: