Page Comparison

The response below indicates a problem with the WRITE request, such as missing mandatory headers, invalid message body, or any other violation of HTTP/1.1 by the POST request. The reason for the error is included in the message body of the response.

HTTP/1.1 400 Bad Request
  Date: Wed, 1 Sept 2012 15:59:02 GMT
  Server: CAStor Cluster/5.0.0
  Content-Type: text/html 
  Content-Length: 24
  CRLF Host header is required.

The response below indicates the WRITE request did not supply the actual content-length, which is required.

HTTP/1.1 411 Length Required
  Date: Wed, 1 Sept 2012 15:59:02 GMT
  Server: CAStor Cluster/5.0.0
  Content-Type: text/html 
  Content-Length: 93
  CRLF WRITE requests must include a Content-Length header specifying 
    the exact byte-length of the content to be stored.

The response indicates the named object already exists or the bucket or domain cannot be found. 

The response below indicates the WRITE request did not succeed because the storage cluster did not have sufficient resources to fulfill it. The specific resource constraint is described in the entity (message-body) of the response.

HTTP/1.1 507 Insufficient Storage
  Date: Wed, 1 Sept 2012 15:59:02 GMT
  Server: CAStor Cluster/5.0.0
  Content-Type: text/html Content-Length: 38
  CRLF Not enough disk space to store requested content.