![]() ![]() The pop receipt is returned from the most recent Get Messages or Update Message operation. The message ID is returned from the previous Get Messages operation. The message ID, an opaque GUID value that identifies the message in the queue.Ī valid pop receipt, an opaque value that indicates that the message has been retrieved. To delete the message, you must have two items of data returned in the response body of the Get Messages operation: The message is later removed from the queue during garbage collection.Īfter a client retrieves a message with the Get Messages operation, the client is expected to process and delete the message. ![]() When you successfully delete a message, it's immediately marked for deletion, and is no longer accessible to clients. Additionally, anyone with a shared access signature who has permission to perform this operation can perform it. The account owner can perform this operation. If the x-ms-client-request-id header isn't present in the request, this header won't be present in the response. The value is at most 1,024 visible ASCII characters. The value of this header is equal to the value of the x-ms-client-request-id header, if it's present in the request. This header can be used to troubleshoot requests and corresponding responses. This header is returned for requests made against version and later.Ī UTC date/time value that indicates the time at which the response was initiated. Indicates the version of Queue Storage used to run the request. For more information, see Troubleshooting API operations. This header uniquely identifies the request that was made, and can be used for troubleshooting the request. All standard headers conform to the HTTP/1.1 protocol specification. The response also includes additional, standard HTTP headers. The response for this operation includes the following headers. For information about status codes, see Status and error codes. Status codeĪ successful operation returns status code 204 (No Content). The response includes an HTTP status code and a set of response headers. For more information, see Monitor Azure Queue 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. 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. ![]() Specifies the authorization scheme, account name, and signature. The following table describes required and optional request headers. For more information, see Setting timeouts for Queue Storage operations. The timeout parameter is expressed in seconds. A valid pop receipt value returned from an earlier call to the Get Messages or Update Message operation. The request URI supports the following parameters. When you make a request against the emulated storage service, specify the emulator host name and Azure Queue Storage port as 127.0.0.1:10001, followed by the emulated storage account name. Replace myaccount with the name of your storage account, myqueue with the name of your queue, and string-value with the value of the pop receipt that has been obtained for the message to be deleted. You can construct the Delete Message request as follows. The Delete Message operation deletes the specified message from the queue. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |