Abort Copy File
Abort Copy File operation cancels a pending
Copy File operation, and leaves a destination file with zero length and full metadata. This operation applies to version 2015-02-21 and newer.
|Enabled file share protocol||Available|
You can construct the
Abort Copy File request as follows. HTTPS is recommended.
Beginning with version 2013-08-15, you can specify a shared access signature for the destination file if it's in the same account as the source file. Beginning with version 2015-04-05, you can also specify a shared access signature for the destination file if it's in a different storage account.
|Method||Request URI||HTTP version|
Replace the path components shown in the request URI with your own, as follows:
||The name of your storage account.|
||The name of your file share.|
||Optional. The path to the parent directory.|
||The name of the file.|
For details on path naming restrictions, see Naming and referencing shares, directories, files, and metadata.
You can specify the following additional parameter on the request URI.
||Optional. The timeout parameter is expressed in seconds. For more information, see Setting timeouts for Azure Files operations.|
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. This operation is available only in versions 2015-02-21 and later.
For more information, see Versioning for the Azure Storage services.
||Required if the destination file has an active lease. Available for versions 2019-02-02 and later.|
||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 Files.|
||Optional. Version 2022-11-02 and later. The Boolean value specifies if a trailing dot present in request url should be trimmed or not. For more information, see Naming and referencing shares, directories, files, and metadata.|
The response includes an HTTP status code and a set of response headers.
A successful operation returns status code 204 (No Content). For information about status codes, see Status and error codes.
The response for this operation includes the following headers. The response also includes 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.|
||Indicates the version of Azure Files used to run the request.|
||A UTC date/time value that indicates the time at which the response was initiated. The service generates this value.|
||You can use this header to troubleshoot requests and corresponding responses. The value of this header is equal to the value of the
Only the account owner can call this operation.
When you cancel a pending
Copy File operation, the destination file's
x-ms-copy-status header is set to
aborted. Canceling a copy operation results in a destination file of zero length. However, the metadata for the destination file will have the new values copied from the source blob or file, or set explicitly in the
Copy File operation call.
You can only cancel a copy operation that is pending. Trying to cancel a copy that has completed, or failed, results in conflict error. Trying to cancel a copy operation by using an incorrect copy ID also results in conflict error.