Instance Configuration Parameters
The following table lists the instance configuration parameters of ROMA Connect.
Parameter |
Description |
---|---|
ratelimit_api_limits |
Default request throttling value applied to all APIs. If no request throttling policy is bound to an API, the total number of times the API can be called is determined by this parameter value. If a request throttling policy has been bound to an API, the total number of times the API can be called is determined by the bound policy. |
request_body_size |
Maximum size of the body allowed in an API request. |
backend_timeout |
Maximum timeout duration for ROMA Connect to send a request to a backend service. |
app_token |
Whether to enable app_token authentication. After this function is enabled, the obtained access token can be used in API requests for authentication during API calling.
|
app_basic |
Whether to enable app_basic authentication. After this function is enabled, you can add the Authorization parameter to an API request to carry the key and secret of an integration application (or the AppKey and AppSecret of a client) for authentication during API calling. |
app_secret |
Whether to enable app_secret authentication. After this function is enabled, you can add the X-HW-ID and X-HW-AppKey parameters to an API request to carry the key and secret of an integration application (or the AppKey and AppSecret of a client) for authentication during API calling. If the app_secret authentication mode is used, the app_api_key authentication mode must be disabled. |
app_route |
Whether to support IP address access. After this function is enabled, APIs in non-DEFAULT groups can be called by using IP addresses. |
cascade |
Whether to enable the API cascading function. After this function is enabled, APIs can be called across instances.
|
default_group_hide |
Whether to hide the DEFAULT group. After this function is enabled, the DEFAULT group is hidden. |
livedata_config |
Custom backend configuration.
|
backend_client_certificate |
Whether to enable two-way authentication for a backend. After this function is enabled, you can configure the two-way authentication for a backend when configuring the backend information during API creation. |
ssl_ciphers |
HTTPS cipher suite that can be configured. You can select the cipher suites as required. |
real_ip_from_xff |
Whether to use the IP addresses in the X-Forwarded-For header as the criterion for access control and request throttling. xff_index: Sequence number of an IP address in the X-Forwarded-For header. The value can be positive, negative, or 0.
For example, assume that the X-Forwarded-For header of a request received by API gateway contains three IP addresses: IP1, IP2, and IP3. If the value of xff_index is 0, IP1 is obtained. If the value of xff_index is 1, IP2 is obtained. If the value of xff_index is –1, IP3 is obtained. If the value of xff_index is –2, IP2 is obtained. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot