检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
Gateway Response Select a response to be displayed if the gateway fails to process an API request. Default: default. Matching Select Prefix match. Authentication Mode API authentication mode. Select None. (None: Not recommended for actual services.
To change this limit of dedicated gateways, go to the Gateway Information page, click the Parameters tab, and modify the ratelimit_api_limits parameter. Parent topic: Calling APIs
If your gateway does not support request throttling 2.0, contact technical support. Parent topic: Using Request Throttling 2.0 for Fine-grained Request Throttling
If your gateway does not support this policy, contact technical support to upgrade the gateway to the latest version. Policy parameters will be stored as plaintext. To prevent information leakage, do not contain sensitive information in these parameters.
Select a dedicated gateway at the top of the navigation pane. Choose API Management > API Groups. Click a group name to go to the Group Information page. On the APIs tab, select the target API and click Publish Latest Version.
Select a dedicated gateway at the top of the navigation pane. In the navigation pane, choose API Management > Credentials. Click the name of the target credential. Under AppCodes, click Add AppCode. Configure the AppCode in the dialog box based on the following table.
Select a dedicated gateway at the top of the navigation pane. In the navigation pane, choose API Management > Credentials. Click Create Credential and configure parameters based on the following table.
Select a dedicated gateway at the top of the navigation pane. In the navigation pane, choose API Management > API Policies. Click the Orchestration Rules tab. Click Create Rule and configure the parameters based on the following table.
Select a dedicated gateway at the top of the navigation pane. In the navigation pane, choose API Management > API Policies. On the Policies tab, click Create Policy. On the Select Policy Type page, select Request Throttling in the Traditional Policy area.
If the gateway supports the authorizer_context_support_num_bool feature, the key value can be a number or a Boolean value. The context field contains custom user data. After successful authentication, the user data is mapped to the backend parameters.
Select a dedicated gateway at the top of the navigation pane. In the navigation pane, choose API Management > API Policies. On the Policies tab, click Create Policy. On the Select Policy Type page, select Signature Key in the Traditional Policy area.
Select a dedicated gateway at the top of the navigation pane. In the navigation pane, choose API Management > API Policies. On the Policies tab, click Create Policy. On the Select Policy Type page, select Proxy Mirror in the Plug-ins area.
It can be key-value pairs, but the key value cannot be a JSON object or an array.If the gateway supports the authorizer_context_support_num_bool feature, the key value can be a number or a Boolean value. The context field contains custom user data.
Users with this permission can use all functions of the dedicated gateways, and shared gateway on the old console.
Select a dedicated gateway at the top of the navigation pane. In the navigation pane, choose API Management > API Policies. On the Policies tab, click Create Policy. On the Select Policy Type page, select Access Control in the Traditional Policy area.
For details about how to create a CORS policy, see CORS"CORS" in the API Gateway User Guide. Figure 8 Example for creating a CORS policy Import signer.js and dependencies to the HTML page.
Precautions The API group and API quotas in API Gateway are sufficient. If you use the title property in Swagger info and OpenAPI info to specify an API group name, the name of a new API group cannot be the same as that of an existing one.
Check whether the IP address is restricted by gateway access control. APIG.0404 Access to the backend IP address has been denied. 403 The backend IP address cannot be accessed.
