Parameter | Description |
Listener Name | Enter a name for the listener. |
Routing Type | Select a routing type. In this example, Intelligent Routing is selected. Intelligent Routing: automatically selects a nearby and healthy endpoint group based on network latency and forwards client requests to the optimal endpoint in the endpoint group. Custom Routing: generates a port mapping table based on the listener port range, the port ranges of the destination endpoint groups, and the IP addresses of endpoints (vSwitches). This way, traffic is routed to specific IP addresses and ports of specified vSwitches. For more information about how to configure a custom routing listener, see Add and manage custom routing listeners. Note Custom routing listeners are in invitational preview. To use custom routing listeners, submit an application to your account manager. After your application is approved, you can use custom routing listeners.
|
Protocol | Select a network transmission protocol for the listener. Valid values: |
Maximum HTTP Version | Select the maximum HTTP version supported by GA. You must select Maximum HTTP Version only if you set Protocol to HTTPS. HTTP/1.1: Compared with HTTP/1.0, HTTP/1.1 supports persistent connections and pipelines, but may encounter head-of-line blocking issues. HTTP/2 (default): HTTP/2 is based on TCP and supports multiplexing and header compression to improve the concurrency of a single connection. HTTP/3: HTTP/3 uses the UDP-based QUIC protocol to resolve head-of-line blocking issues. HTTP/3 supports error recovery and flow control to improve the stability and efficiency of transmission. The latest HTTP/3 version is h3, which is compatible with Google Chrome 87 or later. If you use another browser, make sure that the browser supports HTTP/3.
GA supports forward compatibility for HTTP. For example, if you select HTTP/3 and the client does not support HTTP/3, GA allows the client to send HTTP/2 or HTTP/1.1 requests. Note By default, the feature to select the maximum HTTP version is unavailable. To use the feature, contact your account manager. You cannot select HTTP/3 for subscription Global Accelerator instances. TLS Security Policies takes effect only for non-HTTP/3 connections. HTTP/3 connections use the built-in default security policy.
|
Port Number | Specify a port for the listener to receive and forward requests to endpoints. Valid values: 1 to 65499. You can configure only one listener port for each HTTP or HTTPS listener. Note TCP, HTTP, and HTTPS listeners must use different ports. UDP listeners and HTTP/3 listeners must use different ports.
|
Server Certificate | Select the server certificate that you obtained. This parameter is required only when you set Protocol to HTTPS. Server certificates ensure that data transmission over GA is encrypted. For more information about how to purchase a certificate, see Select and purchase a certificate and Apply for a certificate. If the required service-linked role does not exist when you configure a server certificate for a Global Accelerator instance, the system automatically creates the service-linked role. For more information, see AliyunServiceRoleForGaSsl. |
TLS Security Policies | Select the TLS security policy required by your service. You need to configure a TLS security policy only if you set Protocol to HTTPS. TLS Security Policies takes effect only for non-HTTP/3 connections. HTTP/3 connections use the built-in default security policy. A TLS security policy contains TLS protocol versions and cipher suites that are available for HTTPS. For more information about TLS security policies, see TLS security policies. |
Advanced Settings | Configure the Client Affinity, Idle Connection Timeout Period, Connection Request Timeout, and Custom HTTP Headers parameters. |
Client Affinity | Specify whether to enable client affinity. If you select Source IP Address from the drop-down list, client affinity is enabled. After client affinity is enabled, requests from a specific client IP address are forwarded to the same endpoint. If you select Disabled from the drop-down list, client affinity is disabled. After client affinity is disabled, requests from a specific client IP address may be forwarded to different endpoints.
|
Idle Connection Timeout Period | Specify the timeout period of an idle connection. If no request is received during the timeout period, GA closes the current connection. When a new request is received, GA establishes a new connection. Valid values: 1 to 60. Default value: 15. Unit: seconds. To specify a longer timeout period for pay-as-you-go GA instances, go to Quota Center. Note If your standard GA instance does not support configuring the timeout period of idle connections for intelligent routing listeners, the instance may be using an earlier version. To configure the timeout period of idle connections for intelligent routing listeners, contact your account manager to upgrade your GA instance. |
Connection Request Timeout | Specify the timeout period of a request. If the backend server does not respond within the timeout period, GA returns the HTTP 504 error code to the client. Valid values: 1 to 180. Default value: 60. Unit: seconds. You can specify a longer timeout period for pay-as-you-go GA instances. To increase the quota, go to Quota Center. Note If your standard GA instance does not support configuring the request timeout period for intelligent routing listeners, the instance may be using an earlier version. To configure the request timeout period for intelligent routing listeners, contact your account manager to upgrade your GA instance. |
Custom HTTP Headers | Select the HTTP headers that you want to add. Obtain the GA instance ID by using the GA-ID header
Obtain the information about the acceleration region by using the GA-AP header
Obtain the listening protocol of the GA instance by using the GA-X-Forward-Proto header
Obtain the listening port of the GA instance by using the GA-X-Forward-Port header
Obtain client IP addresses by using the X-Real-IP header
|