Copyright © 2010 Caringo, Inc.All rights reserved 29Version 5.0December 2010Server: CAStor Cluster/5.0.0Location: http://node-ip/name-or-uuidContent-UUID: 41a140b5271dc8d22ff8d027176a0821Content-Type: text/htmlContent-Length: 68CRLFA new content stream has been created as requested. Its URL ishttp://node-ip/name-or-uuidThe preceding response means the DX Storage cluster has stored at least one copy of the suppliedcontent stream. Other nodes, if required, can store additional replicas at a later time. The valueof the Location header gives the URI at which the newly created content stream can be accessedin the cluster. The last part of the URI is the symbolic name or UUID of the stream. For unnamedobjects, this value is repeated as the value of the Content-UUID header field. Note the Content-Typeand Content-Length headers refer to the message payload of the response, if any, not the contentstream itself.HTTP/1.1 301 Moved PermanentlyDate: Wed, 1 Sept 2010 15:59:02 GMTServer: CAStor Cluster/5.0.0Location: http://node-ip/name-or-uuid?auth=valueContent-Length: 0The preceding response means the content can be stored as requested, but another node inthe cluster will complete the WRITE. Furthermore, all future requests of this DX Storage clustershould be made through the new access node until another 301 response is received. There is nomessage-body, so the content length is always 0. The value of the Location header indicates whichnode in the cluster the redirect should go to. The client is expected to send another POST requestusing the exact URI contained in the Location header, including the auth= query argument.HTTP/1.1 307 Temporary RedirectDate: Wed, 1 Sept 2010 15:59:02 GMTServer: CAStor Cluster/5.0.0Location: http://node-ip/name-or-uuid/?auth=B1E1509329C7A5DD90DCF6642DFBContent-Length: 0The 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.6.5. Error Responses to WRITEThe DX Storage cluster might return the following responses when the content length header doesnot match the actual content length, the specified content cannot be written to the cluster, or if thereis a problem with the WRITE request itself.HTTP/1.1 400 Bad RequestDate: Wed, 1 Sept 2010 15:59:02 GMTServer: CAStor Cluster/5.0.0Content-Type: text/htmlContent-Length: 24CRLFHost header is required.The preceding response indicates a problem with the WRITE request, such as missing mandatoryheaders, invalid message body, or any other violation of HTTP/1.1 by the POST request. Thereason for the error is included in the message body of the response.