Unbind Physical Express Tunnel
Last Updated：2020-07-20
Description
Unbind the physical express tunnel from the express tunnel gateway.
Request Structure
PUT /v{version}/etGateway/{etGatewayId}?action&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) |
| etGatewayId | String | Yes | URL parameter | Id of express tunnel gateway |
| action | String | Yes | Query parameter | For the actions executed by the express tunnel gateway instance, the value taken in the interface is unbind. |
| clientToken | String | No | Query parameter | The idempotence Token is a ASCII string with a length not exceeding 64 bits. Refer to ClientToken idempotence for details. |
Note: The unbinding of the physical express tunnel is allowed only when the express tunnel gateway is in the status of "Running". The cloud network parameters are cleared while the physical express tunnel is unbound from the express tunnel gateway.
Return Header
There are no other special headers except the public headers.
Return Parameter
There is no special return parameter.
Request Example
PUT /v1/etGateway/dcgw-4ds9x3kmds88?unbind&clientToken=ac31ef8c-5e41-4k38-9ds0-9de700ds5b20 HTTP/1.1
host: bcc.bj.baidubce.com
content-type: application/json
Authorization: bce-auth-v1/bf427691810a11e8a106475a8496ca04/2018-07-06T11:02:49Z/3600/host;x-bce-date/e84ee938f6466428ff5c16b3562a1cbf3db5928e7f863cedec8820b5d98aa474
connection: Keep-AliveReturn Example
HTTP/1.1 200 OK
x-bce-request-id: f76a08db-59dc-4d6e-841d-b36989d75d15
Date: Mon, 09 Jul 2018 02:18:41 GMT
Content-Type: application/json;charset=UTF-8
Server: BWS