Protocol Category | Protocol | Description | Scenario |
Layer-4 protocol | TCP | Connection-oriented and reliable transport layer protocol. A connection must be established through a three-way handshake before data transmission. It supports session persistence based on client IP address (source IP address) and can obtain the client source IP address. | It is suitable for scenarios that require high reliability and data accuracy but have lower requirements for transmission speed, such as file transfer, email sending and receiving, and remote login. For details, see Configuring UDP and TCP Listeners. |
Layer-4 protocol | UDP | Connectionless transport layer protocol. No connection needs to be established or maintained before data transmission. It supports one-to-one, one-to-many, many-to-one, and many-to-many interactive communication, as well as session persistence based on client IP address (source IP address). | It is suitable for scenarios that require high transmission efficiency but have relatively lower accuracy requirements, such as instant messaging and online video. For details, see Configuring UDP and TCP Listeners. |
Layer-7 protocol | HTTP | Application layer protocol that supports forwarding based on request domain name and URL. | It is suitable for applications that require identification of request content, such as Web applications and App services. For details, see Configuring HTTP and HTTPS Listeners. |
Layer-7 protocol | HTTPS | Encrypted application layer protocol that supports forwarding based on request domain name and URL. It provides a unified certificate management service, allows certificate upload and replacement in the GA2.0 console, and supports one-way and mutual authentication. | It is suitable for HTTP applications that require encrypted transmission. For details, see Configuring HTTP and HTTPS Listeners. |
Port Type | Description | Limit |
Listening port (frontend port) | Port on which Global Acceleration receives requests and forwards them to endpoint nodes. | The configurable range is 1-65499. Within the same global acceleration instance: listener ports of UDP protocols can overlap with those of TCP protocols. For example, you can create both a TCP:80 listener and a UDP:80 listener at the same time. Listener ports cannot be duplicated under the same protocol type. TCP, TCP SSL, HTTP, and HTTPS all belong to the TCP protocol type. For example, you cannot create both a TCP:80 listener and an HTTP:80 listener at the same time. |
Endpoint port (backend port) | Port on which the backend server provides services, used to receive and process traffic from Global Acceleration. Layer-7 listeners support endpoint port configuration. | The configurable range is 1-65499. Within the same global acceleration instance, service ports of different listener protocols can overlap. For example, the HTTP:80 listener and HTTPS:443 listener can be bound to the same port on the same backend server at the same time. |
Health check port | Port on which Global Acceleration sends probe requests to backend servers to check whether the servers are running normally. If the port responds normally, the server is considered healthy. | The configurable range is 1-65499. |
Apakah halaman ini membantu?
Anda juga dapat Menghubungi Penjualan atau Mengirimkan Tiket untuk meminta bantuan.
masukan