HTTPS(PI_HTPS)
Function
The HTTPS (PI_HTPS) record stores information about HTTPS service response time. This is a multi-instance record.
Default and changeable values
Item | Default value | Changeable |
---|---|---|
Collection Interval | 360 | Y |
Collection Offset | 0 | Y |
Log | No | Y |
LOGIF | (Blank) | Y |
ODBC key fields
PI_HTPS_MSR_COND_ID
Lifetime
None
Record size
Fields
View name (Manager name) | Description | Summary rule | Format | Delta | Data source |
---|---|---|---|---|---|
Data Transfer Time (DATA_TRANS_TIME) | Data transfer time (seconds) ((7) in Figure 9-5) | AVG | double | No | Probe Daemon |
DNS Time (DNS_TIME) | Data transfer time (seconds) ((4) in Figure 9-5) | AVG | double | No | Probe Daemon |
HTTP Time (HTTP_TIME) | HTTP time (seconds) ((3) in Figure 9-5) | AVG | double | No | Probe Daemon |
Request Count (REQ_COUNT) | Number of requests issued (count) | AVG | double | No | Probe Daemon |
Server Processing Time (SERV_PROCESS_TIME) | Server processing time (seconds) ((6) in Figure 9-5) | AVG | double | No | Probe Daemon |
Setup Time (SETUP_TIME) | Setup time (seconds) ((2) in Figure 9-5) | AVG | double | No | Probe Daemon |
TCP Connection Time (TCP_CON_TIME) | TCP connection time (seconds), including the time required for establishing an SSL connection ((5) in Figure 9-5) | AVG | double | No | Probe Daemon |
Throughput (THROUGHPUT) | Resource transfer throughput (bits/second). This is determined by the total size of resources and the data transfer time. | AVG | double | No | Probe Daemon |
Total Amount of Data (TOTAL_DATA_SIZE) | The total amount of data transferred between the HTTPS probe and the measurement-target server via the TCP connection (bytes). For the data transferred via an SSL-protected connection, the total amount of text data is calculated. The amount of data associated with server authentication for establishing an SSL connection and the amount of data associated with an SSL handshake are not included. | AVG | double | No | Probe Daemon |
Total Resource Size (TOTAL_RES_SIZE) | Size of acquired resources (bytes) | AVG | double | No | Probe Daemon |
Total Response Time (TOTAL_RESP_TIME) | Total response time (seconds) ((1) in Figure 9-5) | AVG | double | No | Probe Daemon |
The following figure shows the HTTPS sequence.
Figure 9-5 HTTPS sequence
HTTPS operating environment and notes
An HTTPS probe establishes an SSL-protected connection with the server that provides the target service. Then the HTTPS probe issues an HTTP request to the URL specified on the connection, uses the GET method to acquire the page or the POST method to register data, and measures the response time. Note that when the SSL connection is established, server authentication is performed to confirm that the connection target is a reliable HTTP server.
The following describes, and provides notes on, an HTTPS operating environment.
Web authentication
The Basic Authentication method is used.
Cookie
PFM - Agent for Service Response accepts cookies based on Netscape Communication's specifications. The information sent as a cookie from the HTTP server is stored in the Cookie file that is created for each measurement condition. The Cookie files remain undeleted even after measurement is completed. If measurement cannot be performed correctly due to a change made to the contents of a measurement condition, delete the Cookie file for that measurement condition, which can be identified by the measurement condition ID. The following is the naming convention for Cookie files:
cookies_<measurement-condition-ID>
Cookie files are stored in the following folder:
installation-folder\agtv\probe\probedata\http
Program execution
Plug-ins, JavaScripts, and applets are downloaded but not executed.
Depth
For example, specifying a depth of 2 acquires the pages displayed in the resources and frames that are embedded in the page at the specified URL. No linked pages are acquired. PFM - Agent for Service Response repeats the acquisition of resources and frames embedded in the acquired page or frame as many times as the specified value.
For the embedded resources and frames, PFM - Agent for Service Response analyzes the acquired HTML, and acquires the resources and frames that are specified by the value of the tag and attribute shown in the table below.
Table 9-16 Embedded resources and frames to be acquired
Tag name | Attribute name |
---|---|
applet | code |
frame | src |
iframe | src |
img | src |
script | src |
Use of proxy
If acquiring the Web page specified by the URL and the embedded resources and frames involves use of a proxy for only part of the acquisition target, measurement cannot be performed.
Cipher strength
The table below shows the encryption types supported by the HTTPS probe. You cannot access a page protected with unsupported cipher strength.
Table 9-17 Supported encryption types
Cryptographic algorithm | Key length |
---|---|
Triple-DES | 168 |
RC4 | 128 |
RC2 | 128 |
RC4-56 | 56 |
DES | 56 |
RC4-40 | 40 |
RC2-40 | 40 |
Server authentication
For server authentication, PFM - Agent for Service Response verifies the validity period of a server certificate sent from the HTTP server and confirms that the server certificate was issued from an authorized Certificate Authority. To verify the server certificate, the root certificate of either the Certificate Authority that issued the server certificate or its higher-level Certificate Authority is required. Because the root certificate has a validity period, you need to re-install the root certificate before it expires. If there is no root certificate or if the server certificate has expired, server authentication fails.
To install a root certificate, use the following procedure:
Client certificate
PFM - Agent for Service Response sends a client certificate to the HTTP server. The HTTP server then verifies the validity period and confirms that the client certificate was issued from an authorized Certificate Authority. The client certificate and the private key can be obtained in either of the following ways.
The file containing the client certificate and private key must be stored under installation-folder\agtv\probe\cert. The file must be in Base64 encoded X.509 format. If the provided client certificate file is not in Base64 encoded X.509 format, use any tool to convert it to X.509 format.
The following shows how to export a client certificate and its private key by using Internet Explorer 8. Note that the client certificate to be exported must have been specified to allow export of the private key when they were imported to Internet Explorer.
RFC compliance
For the functions that are not compliance with RFCs and the restrictions, see the above notes.