Queries the details of a Network Load Balancer (NLB) listener.
Debugging
Authorization information
The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action
policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:
- Operation: the value that you can use in the Action element to specify the operation on a resource.
- Access level: the access level of each operation. The levels are read, write, and list.
- Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level,
All Resources
is used in the Resource type column of the operation.
- Condition Key: the condition key that is defined by the cloud service.
- Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
Operation | Access level | Resource type | Condition key | Associated operation |
---|---|---|---|---|
nlb:GetListenerAttribute | get |
|
| none |
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
ListenerId | string | Yes | The ID of the listener. | lsn-bp1bpn0kn908w4nbw****@233 |
DryRun | boolean | No | Specifies whether only to precheck the request. Valid values:
| false |
ClientToken | string | No | The client token that is used to ensure the idempotence of the request. You can use the client to generate the value, but you must ensure that it is unique among all requests. ClientToken can contain only ASCII characters. Note
If you do not set this parameter, ClientToken is set to the value of RequestId. The value of RequestId of each API request may be different.
| 123e4567-e89b-12d3-a456-426655440000 |
RegionId | string | No | The ID of the region where the Network Load Balancer (NLB) instance is deployed. You can call the DescribeRegions operation to query the most recent region list. | cn-hangzhou |
Response parameters
Examples
Sample success responses
JSON
format
{
"RequestId": "CEF72CEB-54B6-4AE8-B225-F876FF7BA984",
"RegionId": "cn-hangzhou",
"LoadBalancerId": "nlb-83ckzc8d4xlp8o****",
"ListenerId": "lsn-bp1bpn0kn908w4nbw****@233",
"ListenerProtocol": "TCPSSL",
"ListenerPort": 233,
"StartPort": "233",
"EndPort": "455",
"ListenerDescription": "tcpssl_443",
"ServerGroupId": "sgp-ppdpc14gdm3x4o****",
"IdleTimeout": 900,
"SecurityPolicyId": "tls_cipher_policy_1_0",
"CertificateIds": [
"12315790212_166f8204689_1714763408_70998****"
],
"CaCertificateIds": [
"139a00604ad-cn-east-hangzh****"
],
"CaEnabled": false,
"AlpnEnabled": false,
"AlpnPolicy": "HTTP1Only",
"ProxyProtocolEnabled": false,
"ProxyProtocolV2Config": {
"Ppv2VpcIdEnabled": false,
"Ppv2PrivateLinkEpIdEnabled": false,
"Ppv2PrivateLinkEpsIdEnabled": false
},
"SecSensorEnabled": false,
"ListenerStatus": "Running",
"Cps": 1000,
"Mss": 166,
"Tags": [
{
"TagKey": "ac-cus-tag-4",
"TagValue": "ON"
}
]
}
Error codes
HTTP status code | Error code | Error message | Description |
---|---|---|---|
400 | SystemBusy | System is busy, please try again later. | - |
404 | ResourceNotFound.loadBalancer | The specified resource of loadbalancer is not found. | The specified load balancer resource was not found. Please check the input parameters. |
404 | ResourceNotFound.listener | The specified resource %s is not found. | - |
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation |
---|---|---|
2024-02-04 | The Error code has changed | View Change Details |
2023-12-12 | The Error code has changed. The response structure of the API has changed | View Change Details |
2023-11-27 | The Error code has changed. The response structure of the API has changed | View Change Details |
2023-10-10 | The Error code has changed | View Change Details |
2023-09-26 | The Error code has changed | View Change Details |
2023-09-12 | The Error code has changed | View Change Details |
2023-06-29 | The response structure of the API has changed | View Change Details |