The "rename" action (NS3)
You can use the "rename" action with FileStore (NS3) to target a specific file or symbolic link in order to rename it.
POST /[CP Code]/[path]/[file.ext] HTTP/1.1 Host: [Domain Prefix]-nsu.akamaihd.net X-Akamai-ACS-Action: version=1&action=rename&destination=%2F[CP Code]%2F[path]%2F[new_filename.ext] [Signature Header 1] [Signature Header 2] [Body]
Variable values are as follows:
[CP code]: The unique CP code that represents the root directory in the applicable NetStorage Storage Group.
[path]: The complete path to the directory housing the file to be renamed (if applicable).
[file.ext]: The target file or symlink to be renamed (including its extension, if applicable).
[Domain Prefix]: This is the unique domain prefix set up for the storage group during its creation. It can be viewed in the NetStorage Groups UI in Control Center.
[Signature Header 1]and
[Signature Header 2]: Applicable signature headers.
[Body]: You must also include an applicable request
[Body], which is the case with any “PUT” or “POST” action.
Action header field variables
This action has one required action header field, with the following variables:
rename&destination=/[CP Code]/[path]/[file.ext]: Include the
[CP Code]root, followed by the
[path]destination where the renamed file is to reside. Finally, include the new name
[file.ext]for the object and include the extension, if applicable. Ensure that special characters are query string encoded as required. For example, any forward slashes ("/") would need to be represented as
%2F, in support of query string encoding.