HP StoreAll Storage - Manual (Page 177)

The HTTP command is sent in the form of an HTTP DELETE request.
HTTP syntax
The HTTP request line format is:
DELETE /<urlpath>/<pathname> HTTP/1.1
The equivalent curl command format is:
curl –X DELETE http[s]://<IP_address>:<port>/<urlpath>/<pathname>
See “Using HTTP” (page 108) for information about the IP address, port, and URL path.
Description Parameter
The pathname of the existing file on the HTTP share to be deleted. pathname
Example
curl –X DELETE http://99.226.50.92/ibrix_share1/lab/images/xyz.jpg
This example deletes the existing file called xyz.jpg in the lab/images subdirectory on the
ibrix_share1
HTTP share.
Custom metadata assignment
The API provides commands to define a custom metadata attribute for an existing file or directory
in an HTTP share and to delete an existing custom metadata attribute.
For information about retrieving or querying existing custom metadata already applied to files,
see
“Metadata queries” (page 172) .
Upload custom metadata (add or replace)
This command adds or modifies one or more custom metadata attributes for an existing file or
directory on the HTTP share. If the specified attribute does not exist for the file, it is added to the
custom metadata list for that file or directory. If an attribute already exists, the current value is
replaced with the client’s value.
Custom metadata applied to a directory does not also apply to files or directories in that directory,
only to the directory itself.
Up to 15 metadata attributes can be assigned in one command. However, there is no defined limit
on the number of metadata attributes that can be assigned to a file. To assign more than 15
attributes, send multiple PUT requests for the same file.
The ability to add or replace custom metadata is not currently constrained by WORM/retention
settings.
Although attributes and values may be up to 80 characters each, HTTP request messages have a
practical limit of about 2000 bytes which supersedes these maximums.
The ability to add or replace custom metadata is not currently constrained by file permissions or
the file's WORM setting. If the file's directory is accessible to the API user, custom metadata
operations are allowed, regardless of file permissions or the WORM state of the file.
When custom metadata is added, the file or directory becomes protected from renames or moves
and such actions will be denied, even if all custom metadata is later removed. This protection is
independent of file WORM and retention states.
If the file does not exist, a "500 (Internal Server Error)" HTTP error is returned (not a "404 Not
Found").
The HTTP command is sent in the form of an HTTP PUT request.
StoreAll REST API 177