Set Blob Metadata¶
Set Blob Metadata operation sets user-defined metadata for the specified
blob as one or more name-value pairs.
Set Blob Metadata request may be constructed as follows. HTTPS is
myaccount with the name of your storage account, and
example.com with your endpoint’s domain name or IP address.
|Method||Request URI||HTTP Version|
The following additional parameters may be specified on the request URI.
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. For more information, see Versioning for the Azure Storage services.|
||Optional. Sets a name-value pair for the blob. Each call to this operation replaces all existing metadata attached to the blob. To remove all metadata from the blob, call this operation with no metadata headers. Metadata names must adhere to the naming rules for C# identifiers.|
||Not applicable (Zenko 1.2.1 does not support leasing).|
||Optional. Provides a client-generated, opaque value with a 1 KB character limit that is recorded in the analytics logs when storage analytics logging is enabled. This header is useful for correlating client-side activities with requests received by the server. For more information, see Azure Storage Analytics Logging and Windows Azure Logging: Using Logs to Track Storage Requests.|
This operation also supports the use of conditional headers to set blob metadata only if a specified condition is met. For more information, see Specifying conditional headers for Blob service operations.
The response includes an HTTP status code and a set of response headers.
A successful operation returns status code 200 (OK).
For 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 that you can use to perform operations conditionally. See Specifying conditional headers for Blob service operations for more information. The ETag value will be in quotes.|
||The date/time that the blob was last modified. The date format follows RFC 1123. For more information, see Representation of date/time values in headers. Any write operation on the blob (including updates on the blob’s metadata or properties) changes the last modified time of the blob.|
||This header uniquely identifies the request that was made and can be used for troubleshooting the request. For more information, see Troubleshooting API operations.|
||Indicates the version of the Blob service used to execute the request.|
||A UTC date/time value generated by the service that indicates the time at which the response was initiated.|
||The value of this header is set
||This header can be used to
troubleshoot requests and
corresponding responses. The
value of this header is equal to
the value of the