If the Append Block operation causes the blob to exceed that limit, or if the blob size is already greater than the value specified in this header, the request fails with error code 412 (Precondition Failed). Specifies the maximum length in bytes permitted for the append blob. For more information, see Monitor Azure Blob Storage. We highly recommend that you use this header to correlate client-side activities with requests that the server receives. Provides a client-generated, opaque value with a 1-kibibyte (KiB) character limit that's recorded in the logs when logging is configured. To perform this operation on a blob with an active lease, specify the valid lease ID for this header. ![]() Required if the blob has an active lease. This header is supported in versions or later. Indicates the encryption scope to use to encrypt the request contents. If both Content-MD5 and x-ms-content-crc64 headers are present, the request will fail with error code 400. If the two hashes don't match, the operation will fail with error code 400 (Bad Request). Note that this CRC64 hash isn't stored with the blob. When this header is specified, the storage service compares the hash of the content that has arrived with this header value. ![]() This hash is used to verify the integrity of the append block during transport. A CRC64 hash of the append block content. Note that this MD5 hash isn't stored with the blob. This hash is used to verify the integrity of the block during transport. When the length is not provided, the operation will fail with the status code 411 (Length Required). See the Remarks section for limits in older versions. The block size must be less than or equal to 100 MiB (preview) in size for version and later. The length of the block content in bytes. For more information, see Versioning for the Azure Storage services. Specifies the version of the operation to use for this request. For more information, see Authorize requests to Azure Storage. Specifies the Coordinated Universal Time (UTC) for the request. See Authorize requests to Azure Storage for more information. Specifies the authorization scheme, account name, and signature. The following table describes required and optional request headers. For more information, see Setting timeouts for Azure Blob Storage operations. The timeout parameter is expressed in seconds. PUT method request URIįor more information, see Use the Azurite emulator for local Azure Storage development. When you're making a request against the emulated storage service, specify the emulator hostname and Azure Blob Storage port as 127.0.0.1:10000, followed by the emulated storage account name. Replace myaccount with the name of your storage account. You can construct the Append Block request as follows. ![]() Append Block is supported only on version version or later. The Append Block operation is permitted only if the blob was created with x-ms-blob-type set to AppendBlob. The Append Block operation commits a new block of data to the end of an existing append blob.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |