SalesBuy
1-855-856-7678
Technical SupportSupport
Delete Blob (REST API)
Updated: September 13, 2011
The Delete Blob operation marks the specified blob or snapshot for deletion. The blob is later deleted during garbage collection.
Note that in order to delete a blob, you must delete all of its snapshots. You can delete both at the same time with the Delete Blob operation.
The Delete Blob request may be constructed as follows. HTTPS is recommended. Replace myaccount with the name of your storage account:
| DELETE Method Request URI | HTTP Version |
|---|---|
|
|
HTTP/1.1 |
Emulated Storage Service URI
When making a request against the emulated storage service, specify the emulator hostname and Blob service port as 127.0.0.1:10000, followed by the emulated storage account name:
| DELETE Method Request URI | HTTP Version |
|---|---|
|
|
HTTP/1.1 |
For more information, see About Development Storage and Differences between Development Storage and Cloud Storage Services.
URI Parameters
The following additional parameters may be specified on the request URI.
| Parameter | Description |
|---|---|
|
snapshot |
Optional. The snapshot parameter is an opaque DateTime value that, when present, specifies the blob snapshot to delete. For more information on working with blob snapshots, see Working with Snapshots. |
|
timeout |
Optional. The timeout parameter is expressed in seconds. For more information, see Setting Timeouts for Blob Service Operations. |
Request Headers
The following table describes required and optional request headers.
| Request Header | Description |
|---|---|
|
Authorization |
Required. Specifies the authentication scheme, account name, and signature. For more information, see Authentication for the Windows Azure Storage Services. |
|
Date or x-ms-date |
Required. Specifies the Coordinated Universal Time (UTC) for the request. For more information, see Authentication for the Windows Azure Storage Services. |
|
x-ms-version |
Required for all authenticated requests. For more information, see Versioning for the Blob, Queue, and Table services in Windows Azure. |
|
x-ms-lease-id:<ID> |
Required if the blob has an active lease. To perform this operation on a blob with an active lease, specify the valid lease ID for this header. If a valid lease ID is not specified on the request, the operation will fail with status code 403 (Forbidden). |
|
x-ms-delete-snapshots: {include, only} |
Required if the blob has associated snapshots. Specify one of the following two options:
This header should be specified only for a request against the base blob resource. If this header is specified on a request to delete an individual snapshot, the Blob service returns status code 400 (Bad Request). If this header is not specified on the request and the blob has associated snapshots, the Blob service returns status code 409 (Conflict). |
This operation also supports the use of conditional headers to delete the blob only if a specified condition is met. For more information, see Specifying Conditional Headers for Blob Service Operations.
Request Body
None.
The response includes an HTTP status code and a set of response headers.
Status Code
A successful operation returns status code 202 (Accepted).
For information about status codes, see Status and Error Codes.
Response Headers
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.
| Request Header | Description |
|---|---|
|
x-ms-request-id |
This header uniquely identifies the request that was made and can be used for troubleshooting the request. For more information, see Troubleshooting API Operations. |
|
x-ms-version |
Indicates the version of the Blob service used to execute the request. This header is returned for requests made against version 2009-09-19 and above. |
|
Date |
A UTC date/time value generated by the service that indicates the time at which the response was initiated. |
This operation can be performed by the account owner or by anyone using a Shared Access Signature that has permission to delete the blob.
When a blob is successfully deleted, it is immediately removed from the storage account's index and is no longer accessible to clients. The blob's data is later removed from the service during garbage collection.
If the blob has an active lease, the client must specify a valid lease ID on the request in order to delete it.
If a blob has a large number of snapshots, it's possible that the Delete Blob operation will time out. If this happens, the client should retry the request.
