Item | Description |
Instance name | Enter 1 to 50 characters. Allowed characters are a-z, 0-9, and -. The hyphen (-) cannot be used alone or consecutively, and cannot be placed at the beginning or end. Modification is not supported after creation. |
IPv6 access | If you enable this feature, EdgeOne nodes can be accessed over the IPv6 protocol. |
Chinese MLC-border acceleration | When enabled, it will optimize the access performance for Chinese mainland users. For details, please refer to Cross-Regional Secure Acceleration (Overseas Sites). |
DDoS protection configuration |

Origin group for Origin type, you can specify only self-owned origins. In this case, a COS bucket is not supported as the origin.Item | Description |
Rule ID | Auto-generated, not supported for modification, unique identifier of the rule. |
Forwarding protocol | Forwarding protocol of L4 proxy. Valid values: TCP and UDP. |
Forwarding port | The supported port number ranges from 1 to 64999. You can enter multiple ports separated with semicolons (;) or use a hyphen to enter a port range. The following ports are reserved for internal use, please do not use them: For TCP forwarding protocol: 3943, 3944, 6088, 36000, 56000. For UDP forwarding protocol: 4789, 4790, 6080, 61708. |
Origin type and Origin address | Single origin: If you specify Single origin for Origin type, you can enter the IP address or domain name of a single origin.Origin group: If you specify Origin group for Origin type, you can select an origin from an existing origin group, or create an origin group. |
Origin port | Enter a single port or a port range. If a port range is entered, the forwarding port must also be a port range, and the length of the origin site port range must match that of the forwarding port range. For example, if the forwarding port range is 80-90, the origin site port range can be 80-90 or 90-100. |
Session persistence | As long as an origin server IP remains unchanged, traffic from the same client IP will always be forwarded to the same origin server IP. |
Pass client IP | TOA: Pass client IP addresses by using TCP Option (IPv4 200 IPv6 253). It supports the TCP protocol but not the UDP protocol. For more information, see Passing Real Client IP address Through TOA. Proxy Protocol V1 (Recommended): Pass client IP addresses by using the TCP Header. The V1 edition uses plaintext transmission. It supports the TCP Protocol but not the UDP Protocol. For more information, see Passing Real Client IP address Through SPP. Proxy Protocol V2: Pass client IPs by using the header. V2 uses the binary format and supports both TCP and UDP protocols. The first packet of each TCP connection carries a PPv2 header, while only the first data packet carries the header for UDP.For more information, see Passing Real Client IP Through SPP. Not passed: Real client IPs will not be transferred. |
Rule Tag | Optional, you can enter 1-50 any characters to identify the forwarding rule. |
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback