Release Peer Connection
Last Updated：2020-07-20
Description
Release the peer connection.
- The different accounts can be released by the initiator.
- The prepaid, available and unexpired peer connection cannot be released.
- The prepaid and consultation failed peer connection can be released.
Request Structure
Delete /v{version}/peerconn/{peerConnId}?clientToken={clientToken} HTTP/1.1
Host: bcc.bj.baidubce.com
Authorization: authorization stringRequest Parameter
| Parameter name | Type | Required or not | Parameter position | Description |
|---|---|---|---|---|
| version | String | Yes | URL parameter | API version number (the current value is 1) |
| peerConnId | String | Yes | URL parameter | peer connection ID |
| clientToken | String | No | Query parameter | Idempotence Token is an ASCII string with length not exceeding 64 bytes, for details, please see ClientToken Idempotence |
Return Header
There are no other special headers except the public headers.
Return Parameter
There is no special return parameter.
Request Example
Delete /v1/peerconn/peerconn-9td54fmx143e?clientToken=fc31ef8c-5e41-4k38-9ds0-9def00ds5b60 HTTP/1.1
host: bcc.bj.baidubce.com
authorization: bce-auth-v1/2830b179831d11e8be57233b1de1e808/2018-07-09T02:38:52Z/3600/host;x-bce-account;x-bce-client-ip;x-bce-date;x-bce-request-id;x-bce-security-token/9c4e21651b58c9d37c5c475f82eeea0ee5c209cfbd25d3638b94ce33ed98125bReturn Example
HTTP/1.1 200 OK
x-bce-request-id: f7302165-756d-4c83-bb7a-1d4548fbba8c
Cache-Control: no-cache
Server: BWS