3.2.5.2.1 POST
The file content SHOULD be put into the HTTP request. The protocol does not support resuming uploads.
By default, the maximum size of a file that can be uploaded is 100 MB.
This operation is transported by an HTTP POST.
The operation can be invoked through the following URI:
-
https://<ServerName>/services/builtin/FileContentAccessService.svc/filecontent?path={path}&overwrite={overwrite}
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. The client MUST either pass this header to the server or pass all of the following headers to the client. For more details, refer to section 2.2.2.5. |
|
Authorization |
Optional |
The caller's credential is encoded text that is based on a user name and password. For more details, refer to section 2.2.2.4. |
|
AppName |
Optional |
The application name, as specified in section 2.2.2.1. |
|
AppVersion |
Optional |
The application version, as specified in section 2.2.2.3. |
|
AppPublisherName |
Optional |
The application publisher name, as specified in section 2.2.2.2. |
The response message for this operation can result in one of the following status codes.
|
Status code |
Description |
|---|---|
|
201 |
File uploading successfully completed. |
|
401 |
User is not allowed to access resource. |
|
404 |
The specific resource does not exist. |
|
409 |
An item already exists with the requested new name. |