...
All the request policies run before this policy is applied.
Known Issue
Both the HTTP Cache Response and HTTP Retry policies do not evaluate expressions. The policy always runs regardless of input in the expression fields in the policy dialog.
When you use the HTTP Retry Policy with the Basic Auth policy, the request fails with an error message. This issue only applies to Proxies created after the February 2024 release. Existing Proxies are unaffected.
Workaround: Delete the HTTP Retry Policy.
Settings
Parameter Name | Description | Default Value |
---|---|---|
Label | Required. The name for the API policy. | HTTP Retry |
When this policy should be applied | An expression enabled field that determines the condition to be fulfilled for the API policy to execute. For example, if the value in this field is | N/A |
Retry Condition | Select one of the following retry conditions:
| All Errors |
Maximum Attempts | Enter the number of attempts to retry as an integer. Maximum: 10. | 3 |
Retry Interval (seconds) | Enter the number of seconds for the time to attempt retries as an integer. Accepted Range: 0 - 60 seconds. | 3 |
Retry Timeout (seconds) | Enter the number of seconds for the retry timeout. Maximum: 300 seconds (5 minutes) | 30 |
Automatically Retry on 429 Responses | Select to continue retries for the HTTP response code 429. | Deselected |
Use Retry-After Header for 429 Responses | Select to continue retries when the | Deselected |
Status | Specifies whether the API policy is enabled or disabled. | Enabled |
...