HP StoreAll Storage - Manual (Page 191)

Example: Set a file to WORM and retained with a retention expiration date/time
curl -g –X PUT
"https://99.226.50.92/ibrix_share1/lab/images/xyz.jpg?assign=system::retentionExpirationTime=
1376356584,system::worm='true'"
In this example, the file state is changed to WORM and retained. The retention expiration date/time
is set to 13 Aug 2013 01:16:24. The file system default retention period is ignored.
Example: Set/change the retention expiration date/time without a WORM state transiti
curl -g –X PUT
"https://99.226.50.92/ibrix_share1/lab/images/xyz.jpg?assign=system::retentionExpiration
Time=1376356584"
In this example, a file’s retention expiration date/time is assigned, but no state transition to WORM
is performed.
If the file is not already retained, the atime is assigned this value, and it remains un-retained. But
the value will take effect if the file is ever transitioned to WORM in the future, either manually or
by autocommit. If the file is already retained, the retention expiration date/time will be changed
to this new value. If retention settings prohibit this, an error is returned.
HTTP Status Codes
The following HTTP status codes can be returned by the StoreAll REST API. For error status codes,
check the following files for further information about the error:
•
access_log
•
error_log
The logs are in the following directory, on the Active FM server node of the cluster:
/usr/local/ibrix/httpd/debug/logs
By default, there is no activity written to the access_log file. To enable the HTTP Server to write
entries to the file for every HTTP access from a client, uncomment this line in the file /usr/local/
ibrix/httpd/conf/httpd.conf
:
# CustomLog "debug/logs/access_log" common
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
If no errors are encountered, the status code 200 is returned. 200 (OK)
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
If the URL parser in the StoreAll REST API detects an error in the URL it receives, it returns a 400
error. See the access and error logs for details. 400 (Bad Request)
If the path and filename in the URL does not exist and the request is not a PUT (upload) of a
new file, the StoreAll REST API returns a 404 error. 404 (Not Found)
If the StoreAll REST API encounters an error other than those described previously, it returns a
500 error. See the access and error logs for details. 500 (Internal Server
Error)
StoreAll REST API 191