# Overview

The settings management function is used to manage the configuration of the gateway, including basic settings, error response codes, link tracking, custom authentication headers, Web Client, log settings, service orchestration, Dubbo settings, and dedicated line configuration.

# Settings management

Menu location: Gateway Management > Settings Management. Click the menu to enter the settings management page, as shown in the figure.

manager_gateway_config_query_1

After clicking the Edit button, it becomes editable and the configuration items can be changed, as shown in the figure.

manager_gateway_config_query_2

manager_gateway_config_query_3

# Basic Settings

manager_gateway_config_query_4

Gateway port: The service port of the gateway;

Gateway context: The request context of the gateway, such as: /proxy;

Maximum file upload size: default 100M;

Turn on CORS: Cross-domain Ajax requests can be accepted when turned on;

After changing the basic settings, you need to restart the gateway to take effect.

# Error response code

manager_gateway_config_query_5

Enable HTTP status code: respond to HTTP status code when request error, respond 200 when not enabled, such as: 4xx, 5xx errors;

Error code field name: The error code field name of the response JSON message when the request error occurs. Default value: msgCode;

Error message field name: The error code field name of the response JSON message when a request error occurs. Default value: message.

manager_gateway_config_query_6

Request header: request header field name for link tracking;

ID production strategy: the production strategy of link tracking ID, the default is request ID, optional UUID;

ID prefix: The prefix of the link tracking ID, such as ID: fizz-1234567890.

# Custom authentication header

manager_gateway_config_query_7

app: Default fizz-appid, multiples are separated by commas, the value of the default request header is taken first, if there is no value, the value of the custom request header is taken in order;

Signature: Default fizz-sign, multiples are separated by commas, the value of the default request header is taken first, if there is no value, the value of the custom request header is taken in order;

Timestamp: Default is fizz-ts. Multiple values are separated by commas. The value of the default request header is taken first. If there is no value, the value of the custom request header is taken in order.

# Web Client

manager_gateway_config_query_8

# Log settings

manager_gateway_config_query_9

Interface statistics: Count the number of interfaces when enabled;

Push log: Push node instance logs to the management background when enabled;

Request headers that can be recorded in the log: Request headers for node instance request log records. Multiple requests can be separated by commas.

# Service orchestration

manager_gateway_config_query_10

Output null value: When enabled, the JSON message contains fields with null values. It is not enabled by default;

Request headers added by default: Request headers added by default by the calling interface in orchestration. Multiple headers can be separated by commas.

# Dubbo settings

manager_gateway_config_query_11

Registration center: The registration center used by Dubbo service, such as: zookeeper://127.0.0.1:2181.

# Dedicated line configuration

manager_gateway_config_query_12

Server: When enabled, the gateway provides a dedicated line pairing interface;

Client: When enabled, the gateway will start the dedicated line service, which is responsible for forwarding internal requests to the service provider gateway;

Registration center: The client is registered in the registration center, optional Eureka|Nacos;

manager_gateway_config_query_13

manager_gateway_config_query_14

After the dedicated line configuration is changed, the gateway must be restarted to take effect.

← Interface statistics →