HTTP Status Codes
hideHTTP Responses always contain a numeric HTTP Status Code. Different codes signal different types of responses. The HTTP/1.1 RFC contains a list of all official HTTP Status Codes. A summary of the ones used by Socialtext are below:
The request action was performed successfully and a resource created. The URI of the resource can be found in the Location: header of the HTTP response. HTTP Spec.
This response implies the resource did not exist before.
The requested action was performed successfully but no content is being returned. HTTP Spec.
This response is used when an existing resource is updated.
The request could not be understood by the server due to malformed syntax. The client should not repeat the request without modifications. HTTP Spec.
This status indicates the HTTP request requires authentication. The HTTP response headers will indicate what further steps are necessary to complete authentication. HTTP Spec.
This status indicates the HTTP request was forbidden. This usually happens if you attempt to authenticate but fail to do so. HTTP Spec.
This status indicates entity or collection in the HTTP Request was not found. This usually happens if you have an invalid identification number or name.
The HTTP Method is not allowed on the resource. For example: if you attempt to POST to a URL which does not support POST. HTTP Spec.
You have tried to use an unsupported Standard Representation. In Socialtext's ReST API, this is generally produced if you try to use text/plain with many of the resources.
