HP StoreAll Storage - Manual (Page 243)

Be aware that this log file can grow quickly from client HTTP accesses. Manage the size of this file
so that it does not fill up the local root file system. Enable it only when needed to diagnose HTTP
traffic.
Description Status code
This code is returned if no errors are encountered 200 OK
This code is returned if custom metadata was successfully assigned or WORM/retention properties
were successfully set using the HTTP PUT command 201 Created
If no errors are encountered and there is no content to be returned that fills the Store REST API
query conditions/restrictions, the status code 204 is returned in the message header. 204 No Content
This code is returned if the URL parser in the StoreAll REST API detects an error in the URL it
receives. See the access and error logs for details. 400 Bad Request
This code is returned when trying to worm a file that is already wormed. 403 Forbidden
This code is returned if the path and filename in the URL does not exist and the request is not a
PUT (upload) of a new file. 404 Not Found
This code is returned when attempting to send retentionExpirationTime or worm properties
to a directory or in a file system with retention disabled, or if setting up a custom metadata
without appropriated permissions. 405 Method Not
Allowed
This code is retuned if live and deleted attributes are requested in the same command, or if
more than one retentionExpirationTime parameter is requested in the same command. 409 Conflict
This code is returned if the StoreAll REST API encounters an error other than those described
previously. See the access and error logs for details. 500 Internal
Server Error
This code is returned if the database service is unavailable (overloaded or down). 503 Service
Unavailable
HTTP Status Codes 243