您现在访问的是微软AZURE全球版技术文档网站,若需要访问由世纪互联运营的MICROSOFT AZURE中国区技术文档网站,请访问 https://docs.azure.cn.
Clear Messages
The Clear Messages
operation deletes all messages from the specified queue.
Request
The Clear Messages
request may be constructed as follows. HTTPS is recommended. Replace myaccount with the name of your storage account, and myqueue
with the name of your queue:
Method | Request URI | HTTP Version |
---|---|---|
DELETE |
https://myaccount.queue.core.windows.net/myqueue/messages |
HTTP/1.1 |
Emulated Storage Service URI
When making a request against the emulated storage service, specify the emulator hostname and Queue service port as 127.0.0.1:10001
, followed by the emulated storage account name:
Method | Request URI | HTTP Version |
---|---|---|
DELETE |
http://127.0.0.1:10001/devstoreaccount1/myqueue/messages |
HTTP/1.1 |
URI Parameters
The following additional parameters may be specified on the request URI.
Parameter | Description |
---|---|
timeout |
Optional. The timeout parameter is expressed in seconds. For more information, see Setting Timeouts for Queue Service Operations. |
Request Headers
The following table describes required and optional request headers.
Request Header | Description |
---|---|
Authorization |
Required. Specifies the authentication scheme, account name, and signature. For more information, see Authentication for the Azure Storage Services. |
Date or x-ms-date |
Required. Specifies the Coordinated Universal Time (UTC) for the request. For more information, see Authentication for the Azure Storage Services. |
x-ms-version |
Optional. Specifies the version of the operation to use for this request. For more information, see Versioning for the Azure Storage Services. |
x-ms-client-request-id |
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. Using this header is highly recommended for correlating client-side activities with requests received by the server. For more information, see About Storage Analytics Logging and Azure Logging: Using Logs to Track Storage Requests. |
Request Body
None.
Response
The response includes an HTTP status code and a set of response headers.
Status Code
A successful operation returns status code 204 (No Content).
For information about status codes, see Status and Error Codes.
Response Headers
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.
Request Header | Description |
---|---|
x-ms-request-id |
This header uniquely identifies the request that was made and can be used for troubleshooting the request. For more information, see Troubleshooting API Operations. |
x-ms-version |
Indicates the version of the Queue service used to execute the request. This header is returned for requests made against version 2009-09-19 and later. |
Date |
A UTC date/time value generated by the service that indicates the time at which the response was initiated. |
Response Body
None.
Authorization
Only the account owner may call this operation.
Remarks
If a queue contains a large number of messages, Clear Messages
may time out before all messages have been deleted. In this case the Queue service will return status code 500 (Internal Server Error), with the additional error code OperationTimedOut. If the operation times out, the client should continue to retry Clear Messages
until it succeeds, to ensure that all messages have been deleted.
See Also
Queue Service Error Codes
Authentication for the Azure Storage Services
Status and Error Codes