Delete m3u8 File
Last update：2022-02-15 09:43:26
Delete m3u8 File
Description
This interface provides to delete the specified resource.
Note:
- Deleted files cannot be recovered, please operate with caution.
- During the deletion process, the deletion of some ts files may fail. If you receive a notification of deletion failure, you need to re-trigger the deletion of the m3u8 file until it succeeds.
Request Description
POST /fmgr/deletem3u8
HOST: <MgrDomain>
Authorization:<accessToken>
Header Description
| Parameter | Required | describe |
|---|---|---|
| HOST | Yes | Management domain name , which can be obtained in the user management interface |
| Authorization | Yes | Manage Credentials |
Parameter Description
Request parameters are organized in the following format and submitted as request content:
fops=bucket/<Urlsafe_Base64_Encoded_bucket>/key/<Urlsafe_Base64_Encoded_key>/deletets/<deletets>¬ifyURL=<Urlsafe_Base64_Encoded_notifyUrl>&separate=<Separate>
| Parameter | Required | describe |
|---|---|---|
| fops | Yes | The processing parameter list, the format is as described above, and multiple processing requests are supported at the same time. The parameter lists are separated by ;. Note: When the specified resource does not exist, the returned result is “deletion successful”. |
| bucket | Yes | Specify storage space. <Urlsafe_Base64_Encoded_bucket> is the URL-safe Base64-encoded string for the specified bucket name. |
| key | Yes | Specifies the key to store the resource. <Urlsafe_Base64_Encoded_key> is the URL-safe Base64-encoded string for the key of the specified resource. |
| deletets | no | Specifies whether to associate delete ts files. 0 Do not perform association deletion 1 Delete the associated ts file Note: <1>If this parameter is not set, the default association deletion is performed <2>Only valid for files whose TS access path is a relative path in the m3u8 file format, if the TS address is absolute Path, TS files will not be associated and deleted, please operate with caution <3> For the m3u8 file format where the TS file is an absolute path, it is recommended to parse the content of the m3u8 file first and operate the TS file separately before processing the m3u8 file. |
| notifyURL | no | The processing result is notified of the receiving URL. For the format of the notification content, see the returned content of the task query interface . |
| separate | no | Whether processing Description are notified separately. Set 1 and 0 as option codes: 1: Indicates that notifyURL is notified after each command is executed. 0: Indicates that notifyURL is notified once after all commands are executed . The default value is 0. |
fops parameter example
fops=bucket/bXlidWNrZXQ=/key/SW1hZ2UubTN1OA==/deletets/1;bucket/bXlidWNrZXQ=/key/SW1hZ2UxLm0zdTg=/deletets/0¬ifyURL=aHR0cDovL3Rlc3QuY29tL25vdGlmeVVSbA==&separate=1
Response Description
If the request is successful, a Jsonstring with the following content is returned:
{ "persistentId": <persistentId> }
| Field name | Required | describe |
|---|---|---|
| persistentId | Yes | The task process ID, which can be used to query the task progress. |
If the request fails, a Jsonstring with the following content is returned:
{
"code": "<code string>",
"message": "<ErrMsg string>"
}
| Field name | Required | describe |
|---|---|---|
| code | Yes | HTTP request response code, see HTTP response status code |
| message | Yes | Request failed message |
example
curl -v -X POST -d" fops=bucket/bXlidWNrZXQ=/key/SW1hZ2UubTN1OA==/deletets/1;bucket/bXlidWNrZXQ=/key/SW1hZ2UxLm0zdTg=/deletets/0¬ifyURL=aHR0cDovL3Rlc3QuY29tL25vdGlmeVVSbA==&separate=1" -H "Authorization:86622e227a50d49d858c2494a935bc2e4ac543a7:Y2JmMGY0YTNhZmQxZmVlZGM2ZTA0YTdjNTcyOWQ1NjRkNTExYjg0Yg==" --url "http://mgrDomain/fmgr/deletem3u8"
Is the content of this document helpful to you?
Yes
I have suggestion