SetLoadBalancerHTTPListenerAttribute - ENS - Alibaba Cloud Documentation Center

Modifies the configurations of an HTTP listener.

Operation description

You can call this operation up to 100 times per second per account.
You can call this operation up to 10 times per second per user.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

Debug

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
ens:SetLoadBalancerHTTPListenerAttribute	update	All Resources *	none	none

Request parameters

Parameter	Type	Required	Description	Example
LoadBalancerId	string	Yes	The ID of the Edge Load Balancer (ELB) instance.	lb-5snthcyu1x10g7tywj7iu****
ListenerPort	integer	Yes	The frontend port that is used by the ELB instance. Valid values: 1 to 65535.	8080
Description	string	No	The description of the listener. The description must be 1 to 80 characters in length. Note The value cannot start with `http://` or `https://`.
Scheduler	string	No	The scheduling algorithm. Examples: wrr: Backend servers with higher weights receive more requests than those with lower weights. wlc: Requests are distributed based on the weight and load of each backend server. The load refers to the number of connections on a backend server. If two backend servers have the same weight, the backend server that has fewer connections receives more requests. rr: Requests are distributed to backend servers in sequence. sch: Consistent hashing that is based on source IP addresses. Requests from the same source IP address are distributed to the same backend server. qch: Consistent hashing based on Quick UDP Internet Connection (QUIC) IDs. Requests that contain the same QUIC ID are scheduled to the same backend server. iqch: Consistent hashing based on three specific bytes of iQUIC CID. Requests with the same second, third, and forth bytes are scheduled to the same backend server.	wrr
HealthCheck	string	No	Specifies whether to enable the health check feature. Valid values: on off	on
HealthCheckDomain	string	No	The domain name that is used for health checks. Note This parameter takes effect only if you set HealthCheck to on.	www.aliyundoc.com
HealthCheckURI	string	No	The Uniform Resource Identifier (URI) that is used for health checks. The URI must be 1 to 80 characters in length. Note The URL must start with a forward slash (`/`) and contain characters other than forward slashes (`/`). This parameter takes effect only if you set HealthCheck to on.	/checkpreload.htm
HealthyThreshold	integer	No	The number of consecutive successful health checks that must occur before an unhealthy and inaccessible backend server is declared healthy and accessible. Valid values: 2 to 10. Note This parameter takes effect only if you set HealthCheck to on.	3
UnhealthyThreshold	integer	No	The number of consecutive failed health checks that must occur before a healthy and accessible backend server is declared unhealthy and inaccessible. Valid values: 2 to 10. Note This parameter takes effect only if you set HealthCheck to on.	3
HealthCheckTimeout	integer	No	The timeout period of a health check response. If a backend server does not respond within the specified timeout period, the server fails to pass the health check. Default value: 5. Valid values: 1 to 300. Unit: seconds. Note This parameter takes effect only if you set HealthCheck to on. If the value of the HealthCheckTimeout parameter is smaller than the value of the HealthCheckInterval parameter, the timeout period specified by the HealthCheckTimeout parameter becomes invalid and the value of the HealthCheckInterval parameter is used as the timeout period.	5
HealthCheckConnectPort	integer	No	The port that is used for health checks. Valid values: 1 to 65535. If you leave this parameter empty, the port specified by BackendServerPort is used for health checks. Note This parameter takes effect only if you set HealthCheck to on.	65500
HealthCheckInterval	integer	No	The interval at which health checks are performed. Valid values: 1 to 50. Unit: seconds. Note This parameter takes effect only if you set HealthCheck to on.	2
HealthCheckHttpCode	string	No	The HTTP status code for a successful health check. Valid values: http_2xx (default) http_3xx. http_4xx http_5xx Note This parameter takes effect only if you set HealthCheck to on.	http_2xx
IdleTimeout	integer	No	The timeout period for idle connections. Default value: 15. Valid values: 1 to 60. Unit: seconds. Note If no request is received within the specified timeout period, ELB closes the connection. When another request is received, CLB establishes a new connection.	15
RequestTimeout	integer	No	The timeout period of requests. Default value: 60. Valid values: 1 to 180. Unit: seconds. Note If no response is received from the backend server within the specified timeout period, ELB returns an HTTP 504 error code to the client.	60
HealthCheckMethod	string	No	The HTTP request method for health checks. Examples: head get Note This parameter takes effect only if the HealthCheck parameter is set to on.	head
XForwardedFor	string	No	Specifies whether to use the X-Forwarded-For header to obtain the real IP address of the client. Valid values: on off (default)	on

Response parameters

Parameter	Type	Description	Example
	object	Schema of Response
RequestId	string	The ID of the request.	473469C7-AA6F-4DC5-B3DB-A3DC0DE3C83E

Examples

Sample success responses

JSONformat

{
  "RequestId": "473469C7-AA6F-4DC5-B3DB-A3DC0DE3C83E"
}

Error codes

HTTP status code	Error code	Error message	Description
400	ens.interface.error	An error occurred while call the API.	-
400	Invalid%s	The specified parameter %s is invalid.	-
400	Missing%s	You must specify the parameter %s.	-
400	LoadBalancerNotFound	The input parameter loadBalancerId that is not found.	-
400	IncorrectInstanceStatus	The current status of the resource does not support this operation.	The current operation is not supported. The disk is being reset.
400	ListenerNotFound	The input parameter listener that is not found.	-
400	IncorrectListenerStatus	The current status of the resource does not support this operation.	-
400	NoPermission	Permission denied.	-
400	InvalidParameter.%s	The specified field %s invalid. Please check it again.	-

For a list of error codes, visit the Service error codes.

Change history

Change time	Summary of changes	Operation
2024-06-04	The Error code has changed. The request parameters of the API has changed	View Change Details