Configuring the HTTPS template
A feature that uses the HTTPS template performs the HTTPS operation to measure the time it takes for the NQA client to obtain data from an HTTPS server.
The expected data is checked only when the expected data is configured and the HTTPS response contains the Content-Length field in the HTTPS header.
The status code of the HTTPS packet is a three-digit field in decimal notation, and it includes the status information for the HTTPS server. The first digit defines the class of response.
Before you perform the HTTPS operation, configure the HTTPS server and the SSL client policy for the SSL client. For information about configuring SSL client policies, see Security Configuration Guide.
To configure the HTTPS template:
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Create an HTTPS template and enter its view. | nqa template https name | By default, no HTTPS templates exist. |
3. Specify the URL of the destination HTTPS server. | url url | By default, no URL is specified for the destination HTTPS server. Enter the URL in one of the following formats:
|
4. Specify an HTTPS login username. | username username | By default, no HTTPS login username is specified. |
5. Specify an HTTPS login password. | password { cipher | simple } string | By default, no HTTPS login password is specified. |
6. Specify an SSL client policy. | ssl-client-policy policy-name | By default, no SSL client policy is specified. |
7. (Optional.) Specify the HTTPS version. | version { v1.0 | v1.1 } | By default, HTTPS 1.0 is used. |
8. (Optional.) Specify the HTTPS operation type. | operation { get | post | raw } | By default, the HTTPS operation type is get, which means obtaining data from the HTTPS server. If you set the HTTPS operation type to raw, use the raw-request command to configure the content of the request to be sent to the HTTPS server. |
9. (Optional.) Enter raw request view. | raw-request | This step is required for the raw operation. Every time you enter the raw request view, the previously configured request content is removed. |
10. (Optional.) Enter or paste the content of the HTTPS request for the HTTPS operation. | N/A | This step is required for the raw operation. By default, the HTTPS request content is not specified. |
11. (Optional.) Return to HTTPS template view. | quit | The system automatically saves the configuration in raw request view before it returns to HTTPS template view. |
12. (Optional.) Specify the source IP address for the probe packets. |
| By default, the packets take the primary IP address of the output interface as their source IP address. The source IP address must be the IP address of a local interface, and the interface must be up. Otherwise, no probe packets can be sent out. |
13. (Optional.) Configure the expected data. | expect data expression [ offset number ] | By default, no expected data is configured. |
14. (Optional.) Configure the expected status codes. | expect status status-list | By default, no expected status code is configured. |