API Gateway
- Release Notes and Announcements
- Product Introduction
- Purchase Guide (Discontinued)
- Dedicated Instance Billing
- Resource Pack Billing
- Getting Started
- Operation Guide
- Instance Management
- Service Management
- Creating API
- Custom Domain Name and Certificate
- Backend Upstream
- Verification and Security
- Access Monitoring
- Plugin Usage
- Practical Tutorial
- Development Guide
- Serverless Framework
- Importing APIs
- Generating Application Authentication Signature
- API Documentation
- Making API Requests
- Plugin APIs
- Application APIs
- Other APIs
- Usage Plan APIs
- IP Policy APIs
- Custom Domain Name APIs
- API Document APIs
- OpenAPI APIs
- Key APIs
- Log APIs
- Service APIs
- Throttling Policy APIs
- Documentation and SDK APIs
- Legacy Features
- Key Pair Authentication
Anti-Replay Plugin
Last updated: 2023-12-22 10:02:09
Overview
The anti-replay plugin is provided by API Gateway to protect APIs from replay attacks. You can create an anti-replay plugin and bind it to an API to protect your backend services.
Directions
Step 1. Create a plugin
1. Log in to the API Gateway console.
2. On the left sidebar, click Plugin to enter the plugin list page.
3. Click Create in the top-left corner of the page and select Anti-Replay as the Plugin Type to create an anti-replay plugin.
Parameter | Required | Description |
Forced anti-replay | No | Whether to enable forced anti-replay. It is disabled by default. If you need to enable it, you must add the `x-apigw-nonce` field to the request header. |
Anti-replay period | No | Valid anti-replay period, which is 900 seconds by default. Value range: 1–1800. |
Step 2. Bind an API and make the plugin effective
1. Select the just created plugin in the list and click Bind API in the Operation column.
2. In the Bind API pop-up window, select the service, environment, and the target API.
PluginData
{"force_nonce":true, // Whether to enable forced anti-replay. It is disabled by default. If you need to enable it, you must add the `x-apigw-nonce` field to the request header."nonce_ttl":1 // Valid period of `nonce`, which is 900 seconds by default. Value range: 1–1800.}
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No