Put Range operation writes a range of bytes to a file.
|Enabled file share protocol||Available|
Put Range request may be constructed as follows. We recommend that you use HTTPS.
|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 information about path naming restrictions, see Name and reference shares, directories, files, and metadata.
The following additional parameters may be specified on the request URI.
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.|
||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.|
Specifies the range of bytes to be written. Both the start and end of the range must be specified. This header is defined by the HTTP/1.1 protocol specification.
For an update operation, the range can be up to 4 MiB in size. For a clear operation, the range can be up to the value of the file's full size.
The File service accepts only a single byte range for the
||Required. Specifies the number of bytes being transmitted in the request body. When the
||Optional. An MD5 hash of the content. This hash is used to verify the integrity of the data during transport. When the
||Required. You must specify one of the following options:
||Required if the file has an active lease. Available for version 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 2021-06-08 and later. You may specify one of the following options:
||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 data representing the range to be uploaded.
Sample request: Update byte range
Request Syntax: PUT https://myaccount.file.core.windows.net/myshare/myfile?comp=range HTTP/1.1 Request Headers: x-ms-write: update x-ms-date: Mon, 27 Jan 2014 22:15:50 GMT x-ms-version: 2014-02-14 x-ms-range: bytes=0-65535 Authorization: SharedKey myaccount:4KdWDiTdA9HmIF9+WF/8WfYOpUrFhieGIT7f0av+GEI= Content-Length: 65536
Sample request: Clear byte range
Request Syntax: PUT https://myaccount.file.core.windows.net/myshare/myfile?comp=range HTTP/1.1 Request Headers: Range: bytes=1024-2048 x-ms-write: clear x-ms-date: Mon, 27 Jan 2014 23:37:35 GMT x-ms-version: 2014-02-14 Authorization: SharedKey myaccount:4KdWDiTdA9HmIF9+WF/8WfYOpUrFhieGIT7f0av+GEI=
The response includes an HTTP status code and a set of response headers.
A successful operation returns status code 201 (Created).
For more 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.
||The ETag contains a value which represents the version of the file. The value is enclosed in quotation marks.|
||Returns the date and time the directory was last modified. The date format follows RFC 1123. For more information, see Represent date/time values in headers. Any operation that modifies the share or its properties or metadata updates the last modified time. Operations on files don't affect the last modified time of the share.|
||This header is returned so that the client can check for message content integrity. The value of this header is computed by the File service. It isn't necessarily the same as the value that's specified in the request headers.|
||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 File service version that was used to execute the request.|
||A UTC date/time value that's generated by the service, which indicates the time when the response was initiated.|
||Version 2017-04-17 and later. The value of this header is set to
||This header can be used to troubleshoot requests and corresponding responses. The value of this header is equal to the value of the
||Version 2021-06-08 and later. The last write time for the file, in the ISO 8601 format. Example:
Response Status: HTTP/1.1 201 Created Response Headers: Transfer-Encoding: chunked Content-MD5: sQqNsWTgdUEFt6mb5y4/5Q== Date:Mon, 27 Jan 2014 22:33:35 GMT ETag: "0x8CB171BA9E94B0B" Last-Modified: Mon, 27 Jan 2014 12:13:31 GMT x-ms-version: 2014-02-14 Content-Length: 0 Server: Windows-Azure-File/1.0 Microsoft-HTTPAPI/2.0
Only the account owner may call this operation.
Put Range operation writes a range of bytes to a file. This operation can be called on an existing file only. It can't be called to create a new file. Calling
Put Range with a file name that doesn't currently exist returns status code 404 (Not Found).
To create a new file, call Create File. A file can be up to 4 TiB in size.
Put Range operation is permitted 10 minutes per MiB to complete. If the operation is taking longer than 10 minutes per MiB on average, it times out.
If the file has an active lease, the client must specify a valid lease ID on the request to write a range.
Range update operations
Put Range with the
Update option performs an in-place write on the specified file. Any content in the specified range is overwritten with the update. Each range that's submitted with
Put Range for an update operation may be up to 4 MiB in size. If you attempt to upload a range that's larger than 4 MiB, the service returns status code 413 (Request Entity Too Large).
Range clear operations
Put Range with the
Clear option releases the space in storage as long as the specified range is 512-byte aligned. Ranges that have been cleared are no longer tracked as part of the file and aren't returned in the List Range response. If the specified range isn't 512-byte aligned, the operation writes zeros to the start or end of the range that isn't 512-byte aligned and frees the rest of the range inside that's 512-byte aligned.
Any ranges that haven't been cleared are returned in the List Ranges response. For an example, see the "Sample unaligned clear range" section that follows.
You can call Lease File to obtain an exclusive write lock to the file against other writes for an infinite duration.
SMB client byte range locks
Although the SMB protocol allows byte range locks to manage read and write access to regions of a file, the
Put Range operation doesn't leverage this capability for the specified
x-ms-range value. Instead,
Put Range requires write access to the entire file. This also means that
Put Range fails if an SMB client has a lock on any range within the file. For more information, see Manage file locks.
SMB client directory change notifications
The SMB protocol supports the FindFirstChangeNotification API function that allows applications to detect when changes occur in the file system. It can detect when a file or directory is added, changed, or deleted, and when a file's size, attributes, or security descriptors change. SMB clients that use this API won't receive notifications when a file or directory change happens via the Azure Files REST API. However, changes caused by other SMB clients propagate notifications.
Sample unaligned clear range
Suppose that a file is created with Create File and a single range is written with
Put Range, as follows:
Request Syntax: PUT https://myaccount.file.core.windows.net/myshare/myfile?comp=range HTTP/1.1 Request Headers: x-ms-write: updte x-ms-date: Mon, 27 Jan 2014 22:15:50 GMT x-ms-version: 2014-02-14 x-ms-range: bytes=0-65536 Authorization: SharedKey myaccount:4KdWDiTdA9HmIF9+WF/8WfYOpUrFhieGIT7f0av+GEI= Content-Length: 65536
Performing a List Ranges operation on the file returns the following response body:
<?xml version="1.0" ecoding="utf-8"?> <Ranges> <Range> <Start>0</Start> <End>65536</End> </Range> </Ranges>
Now suppose that an unaligned clear range byte range operation is performed:
Request Syntax: PUT https://myaccount.file.core.windows.net/myshare/myfile?comp=range HTTP/1.1 Request Headers: Range: bytes=768-2304 x-ms-write: clear x-ms-date: Mon, 27 Jan 2014 23:37:35 GMT x-ms-version: 2014-02-14 Authorization: SharedKey myaccount:4KdWDiTdA9HmIF9+WF/8WfYOpUrFhieGIT7f0av+GEI=
A subsequent List Ranges operation on the file returns the following response body:
<?xml version="1.0" encoding="utf-8"?> <Ranges> <Range> <Start>0</Start> <End>1024</End> </Range> <Range> <Start>2048</Start> <End>65535</End> </Range> </Ranges>
Note that zeros have been written to the unaligned space from 768-1024 and 2048-2304.
Put Range isn't supported on a share snapshot, which is a read-only copy of a share. An attempt to perform this operation on a share snapshot fails with 400 (InvalidQueryParameterValue).