CreateForwardingRules - Global Accelerator - Alibaba Cloud Documentation Center

Creates forwarding rules.

Operation description

HTTP and HTTPS listeners of Global Accelerator (GA) support domain name-based and path-based forwarding rules. After an HTTP or HTTPS listener receives a request, the system matches the request against the forwarding conditions in a forwarding rule and then performs the corresponding forwarding action. For example, if you set Host to www.example.com as the forwarding condition and Forward to epg-bp1enpdcrqhl78g6r**** as the forwarding action in a forwarding rule, requests to the www.example.com domain name match this forwarding rule and are forwarded to the epg-bp1enpdcrqhl78g6r**** endpoint group. Before you call this API operation to create a forwarding rule, we recommend that you understand forwarding rules. For more information, see Forwarding rules.

When you call this operation, take note of the following items:

CreateForwardingRules is an asynchronous operation. After you send a request, the system returns the ID of a forwarding rule, but the forwarding rule is still being created in the system background. You can call the ListForwardingRules operation to query the state of the forwarding rule.
- If the forwarding rule is in the configuring state, it indicates that the rule is being created. In this case, you can only perform query operations.
- If the forwarding rule is in the active state, it indicates that the rule is created.
The CreateForwardingRules operation cannot be repeatedly called for the same 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.

Debug

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

Operation: the value that you can use in the Action element to specify the operation on a resource.
Access level: the access level of each operation. The levels are read, write, and list.
Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
Condition Key: the condition key that is defined by the cloud service.
Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.

Operation	Access level	Resource type	Condition key	Associated operation
ga:CreateForwardingRules	Write	Listener acs:ga:{#regionId}:{#accountId}:listener/{#listenerId} Accelerator acs:ga:{#regionId}:{#accountId}:ga/{#acceleratorId}	none	none

Request parameters

Parameter	Type	Required	Description	Example
RegionId	string	Yes	The ID of the region where the GA instance is deployed. Set the value to cn-hangzhou.	cn-hangzhou
ClientToken	string	No	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 different 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.	02fb3da4****
AcceleratorId	string	Yes	The ID of the GA instance.	ga-bp17frjjh0udz4q****
ListenerId	string	Yes	The ID of the listener.	lsr-bp1s0vzbi5bxlx5****
ForwardingRules	object []	Yes	Details about the forwarding rules.	test
Priority	integer	No	The priority of the forwarding rule. Valid values: 1 to 10000. A lower value indicates a higher priority.	1000
RuleConditions	object []	Yes	The forwarding conditions.
RuleConditionType	string	No	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	Host
RuleConditionValue	string	No	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"]`.	["www.example.com", "www.aliyun.com"]
PathConfig	object	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.
Values	array	No	The path. The path must be 1 to 128 characters in length and must start with a forward slash (/). The path can contain only letters, digits, and the following special characters: $ - _ . + / & ~ @ : '. Supported wildcard characters are asterisks () and question marks (?). Note* For GA instances created after July 12, 2022, all forwarding condition types and forwarding action types are supported. We recommend that you use RuleConditionType and RuleConditionValue to query forwarding conditions.
	string	No	The path. The path must be 1 to 128 characters in length and must start with a forward slash (/). The path can contain only letters, digits, and the following special characters: $ - _ . + / & ~ @ : '. Supported wildcard characters are asterisks () and question marks (?). Note* For GA instances created after July 12, 2022, all forwarding condition types and forwarding action types are supported. We recommend that you use RuleConditionType and RuleConditionValue to query forwarding conditions.	/test
HostConfig	object	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.
Values	array	No	The domain name. 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 (?). Note* For GA instances created after July 12, 2022, all forwarding condition types and forwarding action types are supported. We recommend that you use RuleConditionType and RuleConditionValue to query forwarding conditions.
	string	No	The domain name. 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 (?). Note* For GA instances created after July 12, 2022, all forwarding condition types and forwarding action types are supported. We recommend that you use RuleConditionType and RuleConditionValue to query forwarding conditions.	example.com
RuleActions	object []	Yes	The forwarding action.
Order	integer	Yes	The forwarding priority. Note This parameter does not take effect. Ignore this parameter.	20
RuleActionType	string	Yes	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. RemoveHeaderConfig: deletes the header from a request.	ForwardGroup
RuleActionValue	string	No	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 status code to return. 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: `[ ] { } < > # \| &`.	[{"type":"endpointgroup", "value":"epg-bp1enpdcrqhl78g6r****"}]
ForwardGroupConfig	object	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.
ServerGroupTuples	object []	Yes	The information about the endpoint group. Note For GA instances created after July 12, 2022, all forwarding condition types and forwarding action types are supported. We recommend that you call RuleActionType and RuleActionValue to query forwarding actions.
EndpointGroupId	string	Yes	The ID of the endpoint group. Note For GA instances created after July 12, 2022, all forwarding condition types and forwarding action types are supported. We recommend that you call RuleActionType and RuleActionValue to query forwarding actions.	epg-bp1ieei9664r5nv****
ForwardingRuleName	string	No	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.	test
RuleDirection	string	No	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.	request

Response parameters

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

Examples

Sample success responses

JSONformat

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

Error codes

HTTP status code	Error code	Error message	Description
400	NotExist.Listener	The listener does not exist.	The listener does not exist.
400	NotActive.Listener	The state of the listener is not active.	The listener is unstable.
400	NotExist.Accelerator	The accelerated instance does not exist.	The GA instance does not exist.
400	StateError.Accelerator	The state of the accelerated instance is invalid.	The status of the GA instance is invalid.
400	NotExist.BusinessRegion	The business region does not exist.	The business region does not exist.
400	NotExist.BasicBandwidthPackage	You must specify the basic bandwidth package.	You must specify the basic bandwidth package.
400	QuotaExceeded.EndPoint	The maximum number of endpoints is exceeded.	The maximum number of endpoints is exceeded.
400	Exist.EndpointGroup	The endpoint group already exists.	The endpoint group already exists.
400	NoPermission.VpcEndpoint	You are not authorized to perform the operation.	The user does not have permissions to create service linked roles. Contact the Alibaba Cloud account owner or the permission administrator to grant the current user AliyunGlobalAccelerationFullAccess or create custom permission policies for service linked role. The following content describes the detailed information about custom permission policies: ServiceName: vpcendpoint.ga.aliyuncs.com. Service linked role name: AliyunServiceRoleForGaVpc. Endpoint Permission: ram:CreateServiceLinkedRole.
400	QuotaExceeded.ForwardingRule	The number of forwarding rule exceeds the limit.	The number of forwarding rule exceeds the limit.
400	QuotaExceeded.RuleConditionConfig	The number of path and host exceeds the limit.	-
400	RepeatPathAndHost.ForwardingRule	path and host %s repeat	-

For a list of error codes, visit the Service error codes.

Change history

Change time

Summary of changes

Operation

2023-04-20

The Error code has changed

see changesets

Change item	Change content
Error Codes	The Error code has changed.
	delete Error Codes: 400