tencent cloud

Feedback

Supported Matching Types and Actions

Last updated: 2024-01-02 10:42:44

    Supported Matching Types

    Supported matching types are listed in the following tables.
    Note
    1. URL Path and URL Full support wildcard match. If the URL Path is /foo/*/bar, both /foo/example/barand /foo/demo/bar are valid values.
    2. URL Path, URL Full, query string, file extension,file name and HTTP request header support enabling ignoring case (it is disabled by default).
    Type
    Description
    Sample values
    HOST
    Request Host
    www.example.com
    URL Path
    Request URL path
    If you need to match the /example/foo/bar Path, you can fill in: /example/foo/bar;
    If you need to match the /example directory and all files under the directory, you can fill in: /example/*.
    URL Full
    Complete content of the request URL
    https://www.example.com/foo
    Query string
    Query string in the request URL
    Parameter name: key
    Parameter value: value
    File extension
    File extension (file extension) of the request content
    jpg, png, css
    File name
    File name of the request content
    foo.txt
    HTTP request header
    HTTP request header
    HTTP request header name: name
    HTTP request header value: value
    Client geo location
    Country/region of the client IP
    United States
    Request protocol
    Requested protocol type
    HTTPS or HTTP
    All
    Any site request
    N/A

    Operators

    Type
    Description
    Equal to
    The request is equal to a specified value (value of the matching type).
    Not equal to
    The request is not equal to a specified value (value of the matching type).
    Exist
    A specified value exists in the request (HTTP header name or query parameter name).
    Not exist
    A specified value does not exist in the request (HTTP header name or query parameter name).
    Regular expression matching
    URL Path and URL Full support Google RE2 regular expression matching.

    Supported Actions

    Actions refer to a series of feature configurations performed after the requests hit the conditions. The supported actions and matching types are listed in the following tables.

    Cache configuration

    Action
    Description
    Supported Matching Types
    By configuring the cache TTL, you can optimize node cache to improve resource loading and update resources in a timely manner.
    HOST
    URL FULL
    URL Path
    File name
    File extension
    By adjusting the cache period of resources in browsers, you can optimize the browser cache and increase the loading speed of the requested resources.
    HOST
    URL FULL
    URL Path
    File name
    File extension
    Query string
    Client geo location
    A cache key can be customized to suit your needs by setting the query string, HTTP header and URL case, so that requested resources can be loaded faster.
    HOST
    URL FULL
    URL Path
    File name
    File extension
    Query string
    HTTP Request Header
    Client geo location
    You can specify a TTL period for origin response status codes, allowing the node to directly respond with non-2XX codes.
    HOST
    URL FULL
    URL Path
    File name
    File extension
    Query string
    Cached resources are validated via origin-pull before expiration, so that your site can respond to requests more rapidly.
    HOST
    URL FULL
    URL Path
    File name
    File extension
    After offline caching is enabled, when your origin fails, and resources cannot be pulled through origin-pull normally, resources cached on nodes (even expired resources) can be used until the origin recovers.
    HOST
    URL FULL
    URL Path
    File name
    File extension
    Query string
    HTTP Request Header
    Client geo location

    Network optimization

    Action
    Description
    Supported Matching Types
    HTTP/2 (HTTP 2.0) requests are supported to accelerate sites and improve the web performance.
    HOST
    HTTP/3 (QUIC) requests are supported. HTTP/3 (QUIC) is used to accelerate site requests and improve data transfer efficiency and security.
    HOST
    EdgeOne supports the WebSocket protocol that allows the server to proactively send data to the client.
    HOST
    The maximum upload size is the maximum data volume that can be uploaded in a single client request. You can restrict it to improve the data transfer efficiency and optimize the network transfer.
    HOST
    URL FULL
    URL Path
    File name
    File extension
    Query string
    HTTP Request Header
    Smart Compression can automatically compress the resources to Gzip/Brotli files to reduce the files size and shorten the resource loading time.
    HOST
    Smart acceleration refers to smart dynamic routing acceleration. After this feature is enabled, it will detect the node network latency in real time and use the smart algorithm to select the optimal transfer path, so as to handle both static and dynamic client requests more quickly, stably, and securely. Smart dynamic routing minimizes problems such as high network latency, connection errors, and request failures.
    HOST
    Request origin-pull over the HTTP/2 protocol is supported.
    HOST

    HTTPS optimization

    Action
    Description
    Supported Matching Types
    You can use 301 or 302 redirect to redirect HTTP client requests to HTTPS requests and send them to EdgeOne.
    HOST
    Force clients such as browsers to establish connections to edge nodes over HTTPS for global website encryption.
    HOST
    Configure the protocol version and Cipher suite that are allowed to use when the client shakes hands with the edge server TLS as needed.
    HOST
    Pre-cached OCSP responses are sent at the time of TLS handshake to improve the efficiency.
    HOST
    You can specify the protocol that EdgeOne uses in the origin-pull request.
    HOST

    Modifying HTTP header

    Action
    Description
    Supported Matching Types
    You can customize, add, and delete headers in HTTP responses from nodes to clients.
    HOST
    URL FULL
    URL Path
    File name
    File extension
    Query string
    Client geo location
    
    The custom header can carry the real client IP to the origin.
    HOST
    URL FULL
    URL Path
    File name
    File extension
    Query string
    HTTP Request Header
    Client geo location
    The custom header can carry the geographical location information of the client IP to the origin.
    HOST
    Client geo location
    You can customize, add, and delete headers in HTTP origin-pull requests from nodes to the origin.
    HOST
    URL FULL
    URL Path
    File name
    File extension
    Query string
    HTTP Request Header
    Client geo location
    Host header rewriting enables you to rewrite the host header to the actual origin domain when the origin domain is different from the acceleration domain in the load balancing task.
    HOST
    URL FULL
    URL Path
    File name
    File extension
    Query string
    HTTP Request Header
    Client geo location
    Request protocol

    Advanced configuration

    Action
    Description
    Supported Matching Types
    A node redirects the URL requested by the client to the destination URL based on the response status code.
    HOST
    URL FULL
    URL Path
    File name
    File extension
    Query string
    HTTP Request Header
    Client geo location
    As an access control policy, token authentication supports creating rules to validate access and filter out unauthorized access requests. This effectively prevents your site resources from being maliciously hotlinked and thus protects your business.
    HOST
    URL FULL
    URL Path
    File name
    File extension
    Query string
    HTTP Request Header
    Modify Origin
    Configuration of primary and secondary sources, separate Path, and separate region Rules for complex origin-pull strategies.
    HOST + Any matching type below:
    URL Path
    Client country/region
    HTTP Request Header
    Query string
    File extension
    Based on specified rules, this feature rewrites the user request URL received by the node to the destination URL when the node sends the request to the origin server, which doesn't affect the node cache key.
    HOST
    URL FULL
    URL Path
    File name
    File extension
    Query string
    HTTP Request Header
    Client geo location
    You can specify which part of the query string and Cookie to be included in the request when it’s forwarded to the origin.
    HOST
    URL FULL
    URL Path
    File name
    File extension
    Query string
    HTTP Request Header
    Client geo location
    When origin-pull is requested, the redirect will be based on the 302/301 status code of the origin server, and you can specify the maximum number of redirects (which is 3 by default and can be 1-5).
    HOST
    URL FULL
    URL Path
    File name
    File extension
    Query string
    HTTP Request Header
    Client geo location
    You can redirect requests to a custom error page for specific error status codes returned by the origin. The redirection is performed when a 302 is returned.
    HOST
    URL FULL
    URL Path
    File name
    File extension
    Query string
    HTTP Request Header
    Client geo location
    Range GETs can be enabled to reduce the consumption of large file origin-pulls and response time.
    HOST
    URL FULL
    URL Path
    File name
    File extension
    Query string
    HTTP Request Header
    
    Contact Us

    Contact our sales team or business advisors to help your business.

    Technical Support

    Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

    7x24 Phone Support