BatchSetCdnDomainConfig

The operation that you want to perform. Set the value to BatchSetCdnDomainConfig.

The accelerated domain name. Separate multiple accelerated domain names with commas (,).

The features that you want to configure. Format:

• functionName: the name of the feature. This parameter is required. Separate multiple values with commas (,). For more information, see A list of features.
• argName: the feature parameter for functionName. This parameter is required. You can specify multiple feature parameters.
• argValue: the parameter value that is specified for functionName. This parameter is required.
• parentid: the rule condition ID. This parameter is optional. You can use the condition rule engine to create a rule condition. For information, see BatchSetCdnDomainConfig and SetCdnDomainStagingConfig. A rule condition can identify parameters that are included in requests and filter requests based on the identified parameters. After you create a rule condition, a configid is generated. configid can be used as parentId that is referenced by other features. This way, you can combine rule conditions and features for flexible configurations.

If you set parentId to -1, the existing rule conditions in the configurations are deleted.

[{
   "functionArgs": [{
     "argName": "Parameter A", 
     "argValue": Value of parameter A"
    }, 
  {
    "argName": "Parameter B", 
    "argValue": "Value of parameter B"
     }], 
 "functionName": "Feature name"
 "parentId": "Optional, which corresponds to configid of the referenced rule condition"
}]

The following code shows a sample configuration if parentId is not used.

In this example, the origin_request_header feature is used to add back-to-origin HTTP headers, and the rule condition whose configuration ID is 222728944812032 is referenced.

[{
        "functionArgs": [{
            "argName": "header_operation_type",
            "argValue": "add"
        }, {
            "argName": "header_name",
            "argValue": "Accept-Encoding"
        }, {
            "argName": "header_value",
            "argValue": "gzip"
        }, {
            "argName": "duplicate",
            "argValue": "off"
        }],
        "functionName": "origin_request_header"
}]

The following code shows a sample configuration if parentId is used.

In this example, the origin_request_header feature is used to add back-to-origin HTTP headers, and the rule condition whose configuration ID is 222728944812032 is referenced.

[{
        "functionArgs": [{
            "argName": "header_operation_type",
            "argValue": "add"
        }, {
            "argName": "header_name",
            "argValue": "Accept-Encoding"
        }, {
            "argName": "header_value",
            "argValue": "gzip"
        }, {
            "argName": "duplicate",
            "argValue": "off"
        }],
        "functionName": "origin_request_header",
        "parentId": "222728944812032"
}]

The ID of the request.