Copyright © 2010 Caringo, Inc.All rights reserved 33Version 5.0December 2010The preceding response is similar to the 301 response, except the client should continue to use thecurrent node (the one generating this response) for future requests until further notice.7.5. Error Responses to DELETEThe DX Storage cluster might return the following responses when the specified content cannot bedeleted from the cluster or there is a problem with the DELETE request itself.HTTP/1.1 400 Bad RequestDate: Wed, 1 Sept 2010 15:59:02 GMTServer: CAStor Cluster/5.0.0Connection: closeContent-Type: text/htmlContent-Length: 24CRLFHost header is required.The preceding response indicates a problem with the DELETE request, such as missing mandatoryheaders, invalid message body, or any other violation of HTTP/1.1 by the DELETE request. Thereason for the error is included in the message body of the response.HTTP/1.1 404 Not FoundDate: Wed, 1 Sept 2010 15:59:02 GMTServer: CAStor Cluster/5.0.0Content-Length: 56Content-Type: text/htmlCRLFThe requested resource is not available in this cluster.The preceding response indicates the requested content stream could not be located in this cluster.HTTP/1.1 403 ForbiddenDate: Wed, 1 Sept 2010 15:59:02 GMTServer: CAStor Cluster/5.0.0Content-Length: 56Content-Type: text/htmlCRLFThe requested resource cannot be deleted at this time.The preceding response indicates the requested content stream could not be deleted because itscurrent state forbids it. A stream's lifecycle might include periods of time in which users are notallowed to delete it from the cluster.
