The forward settings are used to enable/disable the forward requests. The requests are forwarded to the next server (whose server details has to be provided in the forward text field) to serve the response.

- Protocol :This is used to specify protocol of recording whether it is HTTP or HTTPS.
- Host/IP :Hostname or IP address of the backend server or endpoint server is the server from where the response is captured
- Port :By default, HTTP Port is 80. User can give the another port according to configuration.

## Forward Request Header

The forward request header is the header which is to be forwarded in a request. In forward request header, there are 3 fields which a user has to select accordingly in order to forward a request which are mentioned below:

1. Mode
2. Header
3. Value

### Mode:

In mode, user can select in which mode the request is to be sent. The mode has 3 following options:

1. Add: This option is used to add a new mode into the request header.
2. Modify: This option is used to modify an existing mode in the request header.
3. Delete: This option is used to delete a particular mode in the request header.

### Header and Value:

User can provide the header and values for the request header.

Note:

1. If a user selects the delete option in mode, then they do not need to provide the header values.
2. If a user wants to delete a header, then they can click on the Delete icon in the table.

## SSL Settings

Secure Sockets Layer (SSL) is the standard security technology for establishing an encrypted link between a web server and a browser. This link ensures that all data passed between the web server and browsers remain private and integral. User can provide the following SSL Settings in this section:

1. TLS Version
2. SSL Renegotiation
3. Cipher Suite
4. Server Require Authentication for Client Certification

### 1. TLS Version

a. User needs to provide the TLS version. There are following options which are available:

1. All Version (s)
2. SSL V3
3. TLS 1.0
4. TLS 1.1
5. TLS 1.2

b. Recommended versions (TLSv1.2 and TLSv1.3).

### 2. SSL Renegotiation

- A number of Internet connections require SSL renegotiation, a Secure Sockets Layer/Transport Layer Security process that allows the changing of the details of a handshake after a connection is made with the server.
- There is a checkbox for the SSL Renegotiation, user can enable/disable it.

### 3. Cipher Suites

1. A cipher suite is a set of algorithms that helps to secure a network connection that uses Transport Layer Security (TLS) or its now-deprecated predecessor Secure Socket Layer (SSL).
2. There is a list of cipher suite from where you can select the required ones.

### 4. Server Require Authentication for Client Certification

1. If a user enables this check box, they need to provide the certificate.
2. User can either select the file from the drop-down or can upload it from there local.

Note: If a user wants to upload their file from local, user needs to click on the Choose Choose button.

### 5. Separate Key File Required

1. On selecting the 'Separate Key File Required' checkbox, user needs to upload the key files.
2. This key file will also be saved in the service directory.

Note: If a user wants to upload their file from local, user needs to click on the Choose Choose button.

## Modify Forward Response Settings

- Occurrence count : This property is used when the source value of a search parameter can occur multiple times in a request. It indicates which instance of the value should be extracted.
- Ignore Case :If enabled, response becomes case sensitive.
- Field Name : User need to provide the field name for which they want to replace the values.
- Current Value : Select the current value from the drop down. There are some pre-defined values displayed in the drop down
- Update Value : User can select the updated value from local directory by clicking the Add button. They need to provide the updated value for that field.

#### Note:

Field name and current value should be in the format <Fieldname><currentvalue> will be update to <Fieldname><newvalue> i.e ABCnull to ABC123

## Additional Settings

There are following general settings available in this section:

- Percent of Request to be forwarded :
  - It is the percentage (%) of request is to be forwarded, the remaining will be served in simulated mode.
  - The forward percentage should be in the range (0-100) up to 2 decimal places.
    Example: If you mention the percentage as 20%, then the remaining 80% will be served as a simulate mode.
- Enable Service Time:
  - In Forward mode, since the response is coming from the backend, there is no need to apply service time. However, in some cases, service time may be required and in that case, you can select the ‘Enable Service Time’ checkbox.
  - Response time will the max of service time or the backend response time.
    Example: If the backend response time is 100 ms and the service time is 200 ms, the client request time will be 200 ms.
    If the backend response time is 300 ms and the service time is 200 ms, the client request time will be 300 ms.

- Replace/Add HOST Header in the Forward Request: If the host header is coming in the request, it will be replaced.
- Connection Timeout: User can provide the connection timeout option at the template level also and it will be treated as a high priority.
- Response Timeout: User can provide the response timeout at the template level.