|
Layer 7 monitoring is HTTP protocol listening and HTTPS protocol listening 。 - HTTP application layer protocol: mainly solves how to package data, most commonly Internet Web applications.
- HTTPS application layer protocol encrypts HTTP to prevent unauthorized access. Web applications that need to encrypt transmission.
Configure TCP listening: Configure UDP listening: Parameter description: Front end protocol [port] The front-end protocol and port used to receive requests and forward requests to the back-end server. The range is 1-65535. be careful: In the same load balancing instance, front-end ports cannot be duplicated. Back end protocol [port] The back-end ECS is open to the back-end port for receiving load balancing requests, which is the same as the front-end protocol, with a range of 1-65535. Bandwidth peak In a load balancing instance, it is used to limit the traffic of different monitors. The total peak listening bandwidth of an instance cannot exceed the purchased bandwidth of the instance. When the listening bandwidth is not limited, the total bandwidth of each listening shared instance. Network bandwidth description>> scheduling algorithm It is the scheduling policy of load balancing for requests. Load balancing supports two scheduling algorithms: weighted polling and weighted minimum connections. Weighted polling: The request is allocated according to the weight value set by the backend server. The higher the weight value, the more times it is allocated. Weighted minimum connections: In addition to the weight value to allocate requests, the number of connections to the back-end server is also considered. When the weight value is the same, the backend server with the smaller number of current connections will be assigned to the request. Use Server Groups User defined virtual server groups are forwarded to different servers on the back end of load balancing according to different forwarding requirements, so as to make load balancing more personalized and flexible. Configure Server Group>> be careful: - Turn on the usage server group. This listener will forward traffic to the selected server group. If there are other servers on the backend of the instance, other servers will no longer receive traffic;
- Turn off the usage server group. This listener will forward traffic to all back-end servers.
Two-way authentication Configuration item for HTTPS listening. HTTP listening does not have this option. Bidirectional authentication is a security authentication method of HTTPS protocol, which requires two-way authentication between the server and client. The server certificate and CA certificate need to be configured. Server certificate Configuration item for HTTPS listening. HTTP listening does not have this option. At this time, HTTPS one-way authentication is used, and only the server authentication is used. The server certificate needs to be configured. Automatically start listening after creation Whether to enable the listening immediately after it is created. It is recommended to enable it immediately. Session Persistence Whether session persistence is enabled. Configuration item for HTTP/HTTPS listening Session persistence is to forward requests from the same client to the same back-end server for processing. yes Embed cookies and Rewrite cookies Differences. - Embed cookies. Cookie embedding means that the load balancing instance inserts the SERVERID string into the HTTP/HTTPS message of the client. We need to specify the Timeout During this time, requests from the same client will be transferred to the same backend ECS, and the backend ECS does not need to be modified.
- Overwrite cookies. Rewriting a cookie means that the load balancing instance rewrites the cookie keywords and values in the HTTP/HTTPS message replied to the backend ECS according to certain rules. The content of the cookie value has changed compared with the initial value, and the timeout period of the cookie needs to be set on the backend ECS. We need to specify on load balancing Timeout
be careful: The session of Layer 7 protocol is kept based on cookies. Use the Layer 7 session to enable cookies for clients that need to access the load balancing instance. Get the real IP Customer requests arrive at the back-end server after load balancing, so that the back-end server can obtain the real customer IP address. On by default. Gzip data compression No Enable Gzip compression to compress specific files. At present, Gzip supports the following compression types: text/plain application/x-javascript text/css application/xml text/javascript application/x-httpd-php. Note: Enabling this function can save bandwidth, but because the compression process consumes resources, the number of load balanced connections will decrease slightly. |
