UpdateForwardingRules -

Modifies forwarding rules.

Description

UpdateForwardingRules is an asynchronous operation. After you send a request, the system returns a request ID, but the operation is still being performed in the system background. You can call the ListForwardingRules operation to query the state of a forwarding rule.
- If the forwarding rule is in the configuring state, it indicates that the forwarding rule is being modified. In this case, you can perform only query operations.
- If the forwarding rule is in the active state, it indicates that the forwarding rule is modified.
The UpdateForwardingRules operation cannot be repeatedly called to modify forwarding rules for the same Global Accelerator (GA) instance within a specific period of time.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer. OpenAPI Explorer dynamically generates the sample code of the operation for different SDKs.

Request parameters


Parameter	Type	Required	Example	Description
Action	String	Yes	UpdateForwardingRules	The operation that you want to perform. Set the value to UpdateForwardingRules.
RegionId	String	Yes	cn-hangzhou	The ID of the region where the GA instance is deployed. Set the value to cn-hangzhou.
ClientToken	String	No	02fb3da4****	The client token that is used to ensure the idempotence of the request. You can use the client to generate the value, but you must make sure that it is unique among all requests. ClientToken can contain only ASCII characters. Note If you do not set this parameter, ClientToken is set to the value of RequestId. The value of RequestId may be different for each API request.
AcceleratorId	String	Yes	ga-bp17frjjh0udz4q****	The ID of the GA instance.
ListenerId	String	Yes	lsr-bp1s0vzbi5bxlx5****	The ID of the listener.
ForwardingRules.N.Priority	Integer	Yes	1000	The priority of the forwarding rule. Valid values: 1 to 10000. A lower value indicates a higher priority.
ForwardingRules.N.RuleConditions.N.RuleConditionType	String	Yes	Host	The type of the forwarding conditions. Valid values: Host: domain name Path: path RequestHeader: HTTP header Query: query string Method: HTTP method Cookie: cookie SourceIP: source IP address
ForwardingRules.N.RuleConditions.N.RuleConditionValue	String	No	["www.example.com", "www.aliyun.com"]	The value of the forwarding condition type. You must specify different JSON strings based on the RuleConditionType parameter. If RuleConditionType is set to Host, this parameter specifies a domain name condition. A forwarding rule can contain only one forwarding condition whose type is host. You can specify multiple domain names in a forwarding condition. The relationship between multiple domain names is OR. The domain name must be 3 to 128 characters in length, and can contain letters, digits, hyphens (-), and periods (.). Supported wildcard characters are asterisks () and question marks (?). Example: `["www.example.com", "www.aliyun.com"]`. If RuleConditionType* is set to Path, this parameter specifies a path condition. A forwarding rule can contain multiple forwarding conditions whose types are path. The relationship between multiple path conditions is OR. You can specify multiple paths in a forwarding condition. The relationship between multiple paths is OR. The path must be 1 to 128 characters in length, and must start with a forward slash (/). The path can contain letters, digits, and the following special characters: $ - _ . + / & ~ @ : '. Supported wildcard characters are asterisks () and question marks (?). Example: `["/a", "/b/"]`. If RuleConditionType* is set to RequestHeader, this parameter specifies an HTTP header condition that consists of key-value pairs. The header values in a forwarding condition must be unique. Example: `[{"header1":["value1","value2"]}]`. Key: The key of an HTTP header must be 1 to 40 characters in length, and can contain letters, digits, hyphens (-), and underscores (_). Value: The value of an HTTP header must be 1 to 128 characters in length, and can contain printable characters whose ASCII values are `greater than or equal to 32 and smaller than 127`. The value cannot start or end with a space character. If RuleConditionType is set to Query, this parameter specifies a query string condition that consists of key-value pairs. Example: `[{"query1":["value1"]}, {"query2":["value2"]}]`. Key: The key of an HTTP header must be 1 to 100 characters in length, and can contain printable characters whose ASCII values are `greater than or equal to 32 and smaller than 127`. The key cannot contain uppercase letters, space characters, or the following special characters: `[ ] { } < > \ ; / ? : @ & = + , $ % \| " ^ ~`. Value: The value of an HTTP header must be 1 to 128 characters in length, and can contain printable characters whose ASCII values are `greater than or equal to 32 and smaller than 127`. The value cannot contain uppercase letters, space characters, or the following special characters: `[ ] { } < > \ ; / ? : @ & = + , $ % \| " ^ ~`. If RuleConditionType is set to Method, this parameter specifies an HTTP method condition. Valid values: HEAD, GET, POST, OPTIONS, PUT, PATCH, and DELETE. Example: `["GET", "OPTIONS", "POST"]`. If RuleConditionType is set to Cookie, this parameter specifies a cookie condition that consists of key-value pairs. Example: `[{"cookie1":["value1"]}, {"cookie2":["value2"]}]`. Key: The key of a cookie must be 1 to 100 characters in length, and can contain printable characters whose ASCII values are `greater than or equal to 32 and smaller than 127`. The key cannot contain uppercase letters, space characters, or the following special characters: `# [ ] { } \ \| < > &`. Value: The value of a cookie must be 1 to 128 characters in length, and can contain printable characters whose ASCII values are `greater than or equal to 32 and lower than 127`. The value cannot contain uppercase letters, space characters, or the following special characters: `# [ ] { } \ \| < > &`. If RuleConditionType is set to SourceIP, this parameter specifies a source IP address condition. You can specify IP addresses, such as 1.1.XX.XX/32. You can also specify CIDR blocks, such as 2.2.XX.XX/24. A forwarding rule can contain only one forwarding condition whose type is source IP address. You can specify multiple source IP addresses in a forwarding condition. The relationship between multiple source IP addresses is OR. Example: `["1.1.XX.XX/32", "2.2.XX.XX/24"]`.
ForwardingRules.N.RuleConditions.N.PathConfig	Map	No		The configuration of the path. Note We recommend that you do not use this parameter. We recommend that you use the RuleConditionType and RuleConditionValue parameters to configure forwarding conditions.
ForwardingRules.N.RuleConditions.N.HostConfig	Map	No		The configuration of the domain name. Note We recommend that you do not use this parameter. We recommend that you use the RuleConditionType and RuleConditionValue parameters to configure forwarding conditions.
ForwardingRules.N.RuleActions.N.Order	Integer	Yes	20	The forwarding priority. Note This parameter does not take effect. Ignore this parameter.
ForwardingRules.N.RuleActions.N.RuleActionType	String	Yes	ForwardGroup	The type of the forwarding action. Valid values: ForwardGroup: forwards a request. Redirect: redirects a request. FixResponse: returns a fixed response. Rewrite: rewrites a request. AddHeader: adds a header to a request. RemoveHeader: deletes the header of a request.
ForwardingRules.N.RuleActions.N.RuleActionValue	String	No	[{"type":"endpointgroup", "value":"epg-bp1enpdcrqhl78g6r****"}]	The value of the forwarding action type. You must specify different JSON strings based on the RuleActionType parameter. A forwarding rule can contain only one forwarding action whose type is ForwardGroup, Redirect, or FixResponse. You must specify a forwarding action whose type is Rewrite, AddHeader, or RemoveHeader before a forwarding action whose type is ForwardGroup. If RuleActionType is set to ForwardGroup, this parameter specifies the information of a virtual endpoint group. You can forward requests to only one virtual endpoint group. Example: `{"type":"endpointgroup", "value":"epg-bp1enpdcrqhl78g6r**"}`. `type`: set this parameter to `endpointgroup`. `value`: set this parameter to the ID of a virtual endpoint group. If RuleActionType is set to Redirect, this parameter specifies redirecting configurations. You cannot leave all of the following parameters empty or configure all of these parameters to use the default values for a forwarding action whose type is Redirect*: `protocol`, `domain`, `port`, `path`, and `query`. Example: `{"protocol":"HTTP", "domain":"www.example.com", "port":"80", "path":"/a","query":"value1", "code":"301" }`. `protocol`: the protocol of requests after the requests are redirected. Valid values: `${protocol}` (default), `HTTP`, and `HTTPS`. `domain`: the domain name to which requests are redirected. Default value: `${host}`. You can also enter a domain name. The domain name must be 3 to 128 characters in length, and can contain only letters, digits, and the following special characters: `. - ? = ~ _ - + / ^ ! $ & \| ( ) [ ]`. `port`: the port to which requests are redirected. Default value: `${port}`. You can enter a port number that ranges from 1 to 63335. `path`: the path to which requests are redirected. Default value: `${path}`. The path must be 1 to 128 characters in length. To use a regular expression, the path can contain letters, digits, and the following special characters: `. - _ / = ? ~ ^ * $ : ( ) [ ] + \|`. The path must start with a tilde (~). If you do not want to use a regular expression, the path can contain letters, digits, and the following special characters: `. - _ / = ? :`. The path must start with a forward slash (/). `query`: the query string of the requests to be redirected. Default value: `${query}`. You can also specify a query string. The query string must be 1 to 128 characters in length, and can contain printable characters whose ASCII values are `greater than or equal to 32 and smaller than 127`. The query string cannot contain uppercase letters, space characters, or the following special characters: `[ ] { } < > # \| &`. `code`: the redirecting code. Valid values: `301`, `302`, `303`, `307`, and `308`. If RuleActionType is set to FixResponse, this parameter specifies a fixed response. Example: `{"code":"200", "type":"text/plain", "content":"dssacav" }`. `code`: the HTTP response status code. The response status code must be one of the following numeric strings: `2xx`, `4xx`, and `5xx`. The letter `x` indicates a number from 0 to 9. `type`: the type of the response content. Valid values: text/plain, text/css, text/html, application/javascript, and application/json. `content`: the response content. The response content cannot exceed 1,000 characters in length and does not support Chinese characters. If RuleActionType is set to AddHeader, this parameter specifies an HTTP header to be added. If a forwarding rule contains a forwarding action whose type is AddHeader, you must specify another forwarding action whose type is ForwardGroup. Example: `[{"name":"header1","type":"userdefined", "value":"value"}]`. `name`: the name of the HTTP header. The name must be 1 to 40 characters in length, and can contain letters, digits, hyphens (-), and underscores (_). The name of the HTTP header specified by AddHeader must be unique and cannot be the same as the name of the HTTP header specified by RemoveHeader. `type`: the content type of the HTTP header. Valid values: `user-defined`, `ref`, and `system-defined`. `value`: the content of the HTTP header. You cannot leave this parameter empty. If you set `type` to `user-defined`, the content must be 1 to 128 characters in length, and can contain printable characters whose ASCII values are `greater than or equal to 32 and smaller than 127`. The content can contain letters, digits, hyphens (-), and underscores (_). The content cannot start or end with a space character. If you set `type` to `ref`, the content must be 1 to 128 characters in length, and can contain letters, digits, hyphens (-), and underscores (_). The content cannot start or end with a space character. If you set `type` to `system-defined`, only `ClientSrcIp` is supported. If RuleActionType is set to RemoveHeader, this parameter specifies an HTTP header to be removed. If a forwarding rule contains a forwarding action whose type is RemoveHeader, you must specify another forwarding action whose type is ForwardGroup. The header must be 1 to 40 characters in length, and can contain letters, digits, hyphens (-), and underscores (_). Example: `["header1"]`. If RuleActionType is set to Rewrite, this parameter specifies the rewriting configuration. If a forwarding rule contains a forwarding action whose type is Rewrite, you must specify another forwarding action whose type is ForwardGroup. Example: `{"domain":"value1", "path":"value2", "query":"value3"}`. `domain`: the domain name to which requests are redirected. Default value: `${host}`. You can also enter a domain name. The domain name must be 3 to 128 characters in length, and can contain only lowercase letters, digits, and the following special characters: `. - ? = ~ _ - + / ^ * ! $ & \| ( ) [ ]`. `path`: the path to which requests are redirected. Default value: `${path}`. The path must be 1 to 128 characters in length. To use a regular expression, the path can contain letters, digits, and the following special characters: `. - _ / = ? ~ ^ * $ : ( ) [ ] + \|`. The path must start with a tilde (~). If you do not want to use a regular expression, the path can contain letters, digits, and the following special characters: `. - _ / = ? :`. The path must start with a forward slash (/). `query`: the query string of the requests to be redirected. Default value: `${query}`. You can also specify a query string. The query string must be 1 to 128 characters in length, and can contain printable characters whose ASCII values are `greater than or equal to 32 and smaller than 127`. The query string cannot contain uppercase letters, space characters, or the following special characters: `[ ] { } < > # \| &`.
ForwardingRules.N.RuleActions.N.ForwardGroupConfig	Map	No		The forwarding configurations. Note We recommend that you do not use this parameter. We recommend that you use the RuleActionType and RuleActionValue parameters to configure forwarding actions.
ForwardingRules.N.ForwardingRuleId	String	Yes	frule-bp1dii16gu9qdvb34****	The ID of the forwarding rule.
ForwardingRules.N.ForwardingRuleName	String	No	test	The name of the forwarding rule. The name must be 2 to 128 characters in length, and can contain letters, digits, periods (.), underscores (_), and hyphens (-). The name must start with a letter.
ForwardingRules.N.RuleDirection	String	No	request	The direction in which the rule takes effect. You do not need to set this parameter. By default, this parameter is set to request, which indicates that the rule takes effect on requests.

Response parameters


Parameter	Type	Example	Description
ForwardingRules	Array of ForwardingRules		Details about the forwarding rules.
ForwardingRuleId	String	frule-bp1dii16gu9qdvb34****	The ID of the forwarding rule.
RequestId	String	64ADAB1E-0B7F-4FD8-A404-3BECC0E9CCFF	The ID of the request.

Examples

Sample requests

http(s)://[Endpoint]/?Action=UpdateForwardingRules
&RegionId=cn-hangzhou
&ClientToken=02fb3da4****
&AcceleratorId=ga-bp17frjjh0udz4q****
&ListenerId=lsr-bp1s0vzbi5bxlx5****
&ForwardingRules=[{"Priority":1000,"RuleConditions":[{"RuleConditionType":"Host","RuleConditionValue":"[\"www.example.com\", \"www.aliyun.com\"]"}],"RuleActions":[{"Order":20,"RuleActionType":"ForwardGroup","RuleActionValue":"[{\"type\":\"endpointgroup\", \"value\":\"epg-bp1enpdcrqhl78g6r****\"}]"}],"ForwardingRuleId":"frule-bp1dii16gu9qdvb34****","ForwardingRuleName":"test","RuleDirection":"request"}]
&<Common request parameters>

Sample success responses

XML format

HTTP/1.1 200 OK
Content-Type:application/xml

<UpdateForwardingRulesResponse>
    <ForwardingRules>
        <ForwardingRuleId>frule-bp1dii16gu9qdvb34****</ForwardingRuleId>
    </ForwardingRules>
    <RequestId>64ADAB1E-0B7F-4FD8-A404-3BECC0E9CCFF</RequestId>
</UpdateForwardingRulesResponse>

JSON format

HTTP/1.1 200 OK
Content-Type:application/json

{
  "ForwardingRules" : [ {
    "ForwardingRuleId" : "frule-bp1dii16gu9qdvb34****"
  } ],
  "RequestId" : "64ADAB1E-0B7F-4FD8-A404-3BECC0E9CCFF"
}

Error codes


HttpCode	Error code	Error message	Description
400	NotExist.Listener	The listener does not exist.	The error message returned because the specified listener does not exist.
400	NotActive.Listener	The state of the listener is not active.	The error message returned because the specified listener is unstable.
400	NotExist.Accelerator	The accelerated instance does not exist.	The error message returned because the specified GA instance does not exist.
400	NotExist.BusinessRegion	The business region does not exist.	The error message returned because the specified region does not exist.
400	NotExist.BasicBandwidthPackage	You must specify the basic bandwidth package.	The error message returned because no basic bandwidth plan is specified.
400	QuotaExceeded.EndPoint	The maximum number of endpoints is exceeded.	The error message returned because the number of endpoints has reached the upper limit.
400	Exist.EndpointGroup	The endpoint group already exists.	The error message returned because the specified endpoint group already exists.
400	NoPermission.VpcEndpoint	You are not authorized to perform the operation.	The error message returned because you are not authorized to create the service-linked role. Contact the owner of the Alibaba Cloud account or the administrator to attach the AliyunGlobalAccelerationFullAccess policy or a custom permission policy that grants the permissions to create the required service-linked role to your RAM user. In the custom policy, the service name must be set to vpcendpoint.ga.aliyuncs.com, the service-linked role to AliyunServiceRoleForGaVpcEndpoint, and the permissions to ram:CreateServiceLinkedRole.

For a list of error codes, visit the API Error Center.