Adding a Forwarding Rule
Function
This API is used to add a forwarding rule.
Constraints
If the action of 17policy is set to Redirect to another listener, 17rule cannot be created.
Calling Method
For details, see Calling APIs.
URI
POST /v3/{project_id}/elb/l7policies/{l7policy_id}/rules
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
l7policy_id |
Yes |
String |
Specifies the forwarding policy ID. |
project_id |
Yes |
String |
Specifies the project ID. |
Request Parameters
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
X-Auth-Token |
Yes |
String |
Specifies the token used for IAM authentication. |
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
rule |
Yes |
CreateRuleOption object |
Specifies the forwarding rule. |
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
admin_state_up |
No |
Boolean |
Specifies the administrative status of the forwarding rule. The default value is true. This parameter is unsupported. Please do not use it. |
compare_type |
Yes |
String |
Specifies how requests are matched with the forwarding rule. Values:
Note:
|
key |
No |
String |
Specifies the key of match content. For example, if the request header is used for forwarding, key is the request header. This parameter is unsupported. Please do not use it. Minimum: 0 Maximum: 255 |
value |
Yes |
String |
Specifies the value of the match content. For example, if a domain name is used for matching, value is the domain name.
Minimum: 1 Maximum: 128 |
project_id |
No |
String |
Specifies the project ID. Minimum: 1 Maximum: 32 |
type |
Yes |
String |
Specifies the match content. The value can be one of the following:
|
invert |
No |
Boolean |
Specifies whether reverse matching is supported. The value can be true or false (default). This parameter is unsupported. Please do not use it. |
conditions |
No |
Array of CreateRuleCondition objects |
Specifies the matching conditions of the forwarding rule. This parameter is available only when enhance_l7policy_enable is set to true. If conditions is specified, parameters key and value will not take effect, and the conditions value will contain all conditions configured for the forwarding rule. The keys in the list must be the same, whereas each value must be unique. |
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
key |
No |
String |
Specifies the key of match item.
All keys in the conditions list in the same rule must be the same. Minimum: 1 Maximum: 128 |
value |
Yes |
String |
Specifies the value of the match item.
All values of the condition list in a fowwarding rule must be unique. Minimum: 1 Maximum: 128 |
Response Parameters
Status code: 201
Parameter |
Type |
Description |
---|---|---|
request_id |
String |
Specifies the request ID. The value is automatically generated. |
rule |
L7Rule object |
Specifies the forwarding rule. |
Parameter |
Type |
Description |
---|---|---|
admin_state_up |
Boolean |
Specifies the administrative status of the forwarding rule. The default value is true. This parameter is unsupported. Please do not use it. |
compare_type |
String |
Specifies how requests are matched with the domain name or URL.
|
key |
String |
Specifies the key of the match content. Minimum: 1 Maximum: 255 |
project_id |
String |
Specifies the project ID. |
type |
String |
Specifies the type of the forwarding rule. The value can be one of the following:
Note: If type is set to HOST_NAME, PATH, METHOD, and SOURCE_IP, only one forwarding rule can be created for each type. If type is set to HEADER and QUERY_STRING, multiple forwarding rules can be created for each type. |
value |
String |
Specifies the value of the match item. For example, if a domain name is used for matching, value is the domain name. This parameter will take effect only when conditions is left blank.
Minimum: 1 Maximum: 128 |
provisioning_status |
String |
Specifies the provisioning status of the forwarding rule. The value can only be ACTIVE (default), PENDING_CREATE, or ERROR. This parameter is unsupported. Please do not use it. |
invert |
Boolean |
Specifies whether reverse matching is supported. The value is fixed at false. This parameter can be updated but will not take effect. |
id |
String |
Specifies the forwarding policy ID. |
conditions |
Array of RuleCondition objects |
Specifies the matching conditions of the forwarding rule. This parameter will take effect when enhance_l7policy_enable is set to .true. If conditions is specified, key and value will not take effect, and the value of this parameter will contain all conditions configured for the forwarding rule. The keys in the list must be the same, whereas each value must be unique. |
created_at |
String |
Specifies the time when the forwarding rule was added. The format is yyyy-MM-dd'T'HH:mm:ss'Z' (UTC time). |
updated_at |
String |
Specifies the time when the forwarding rule was updated. The format is yyyy-MM-dd'T'HH:mm:ss'Z' (UTC time). |
Parameter |
Type |
Description |
---|---|---|
key |
String |
Specifies the key of match item.
All keys in the conditions list in the same rule must be the same. Minimum: 1 Maximum: 128 |
value |
String |
Specifies the value of the match item.
All values of the condition list in a fowwarding rule must be unique. Minimum: 1 Maximum: 128 |
Example Requests
Creating a forwarding rule and setting type to PATH*
POST https://{ELB_Endpoint}/v3/{99a3fff0d03c428eac3678da6a7d0f24}/elb/l7policies/cf4360fd-8631-41ff-a6f5-b72c35da74be/rules { "rule" : { "compare_type" : "EQUAL_TO", "type" : "PATH", "value" : "/bbb.html" } }
Example Responses
Status code: 201
Normal response to POST requests.
{ "rule" : { "compare_type" : "EQUAL_TO", "provisioning_status" : "ACTIVE", "project_id" : "99a3fff0d03c428eac3678da6a7d0f24", "invert" : false, "admin_state_up" : true, "value" : "/bbb.html", "key" : null, "type" : "PATH", "id" : "84f4fcae-9c15-4e19-a99f-72c0b08fd3d7" }, "request_id" : "3639f1b7-f04b-496e-9218-ec5a9e493f69" }
Status Codes
Status Code |
Description |
---|---|
201 |
Normal response to POST requests. |
Error Codes
See Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.