3.3.5.6.1 POST
The POST operation changes the name of an existing item.
This operation is transported by an HTTP POST.
The operation can be invoked through the following URI:
-
https://<ServerName>/services/builtin/fileoperationservice.svc/item/rename?path={path}&newname={newname}
The request message for this operation contains the following HTTP headers.
|
Request header |
Usage |
Value |
|---|---|---|
|
Canary |
Optional |
The value returned in the logon Response Canary header. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, see section 2.2.2.5. |
|
Authorization |
Optional |
The caller's credential is encoded text that is based on user name and password. For more details, see section 2.2.2.4. |
|
AppName |
Optional |
Application name. For more details, see section 2.2.2.1. |
|
AppVersion |
Optional |
Application version. For more details, see section 2.2.2.3. |
|
AppPublisherName |
Optional |
Application publisher name. For more details, see section 2.2.2.2. |
The response message for this operation can result in the following status codes.
|
Status code |
Description |
|---|---|
|
200 |
Operation successfully completed. |
|
400 |
One or more parameters are not valid. |
|
401 |
Access to the requested resource is denied. |
|
404 |
The path does not exist. |
|
409 |
File item with the new name exists. |