Delete Managed File or Directory
Removes an existing file or directory of a specific Managed File ID (or Name) from the File Store.
Request takes no content, and on success returns a response containing the result of the request for removal.
Request
Method Type: |
GET |
---|---|
URI: | |
Content: | – |
Content Type: |
– |
Add. Headers: |
If server security settings are enabled, then one of the following:
|
Parameters
Path
Name | Required | Type | Default Value | Description |
---|---|---|---|---|
fileId |
– |
– |
– |
The Managed File ID (or Name) of the file or directory in File Store |
Response
Success
The following lists status codes indicative of a successful response:
Status Code | Content | Content-Type | Add. Headers | Description |
---|---|---|---|---|
200 OK |
Result of request for removal | text/plain | – | Removal of file or directory successfully requested from File Store |
Error
The following lists status codes indicative of a failed or error response:
Status Code | Content | Content-Type | Add. Headers | Description |
---|---|---|---|---|
400 |
JSON Error specifying error message |
application/json |
|
Deletion failed / File still required by OL Connect |
401 Unauthorized |
JSON Error specifying error message |
application/json |
WWW-Authenticate – BASIC (Basic Authentication credentials are accepted) |
Server authentication has failed. Response when either:
|
403 Forbidden |
JSON Error specifying error message |
application/json |
– |
Server authentication has succeeded, but user authorization for this specific method has failed. Response when authentication of the credentials or the authorization token specified in the request headers has succeeded, but the user associated with the credentials or the authorization token specified has insufficient role assignment/privileges. |
404 |
JSON Error specifying error message |
application/json |
– |
Invalid Managed File ID |
500 Internal Server Error |
JSON Error specifying error message |
application/json |
|
Connection refused |