Starting an HTTP/2 CC Test
This test establishes a large number of TCP connections (three-way handshake), loops complete HTTP/2 transactions (HTTP/2 request and response), and closes the TCP connection.
To start an HTTP/2 CC test:
- Go to Cases > Performance Testing > HTTP/2 > CC to display the test case summary page.
- Click + Create New to display the Select case options dialog box.
- In the popup dialog, for the Network Config option, select the network template you have created in Cases > Security Testing > Objects > Networks. Then the network related options will automatically be filled. See Using network configuration templates for how to create a network template.
- Select a Certificate Group if applicable.
- Click OK to continue.
- Configure the test case options as described below.
- Click Start to run the test case.
FortiTester saves the configuration automatically so you can run the test again later. You can also click Save to save the test case without running it.
|
Tip 1: You can also copy an existing case, and change its settings to create a new case. In the case list, click Clone to clone the configuration. Only the case name is different from the original case. Tip 2: You can add or edit a comment when the test is running. This comment can be used to search for the test result in the Results page. This is useful especially when the test runs for a long time. |
HTTP/2 Test Case configuration generic information
HTTP/2 Test Case configuration specific to CC
| Settings | Guidelines | ||
|---|---|---|---|
| Client Profile | |||
|
Send Goaway |
The GOAWAY frame (type=0x7) is used to initiate shutdown of a connection or to signal serious error conditions. |
||
| Max Data Frame Size | The maximum DATA frame payload size that the client can send in bytes. | ||
| Max Concurrent Streams per Connection | The maximum concurrent streams per connection that the client allows the DUT to create. | ||
| Override Flow Control | Select to enable the HTTP2 flow control fields, Connection Window Size, Stream Window Size, and Send WINDOW_UPDATE. | ||
| Connection Window Size | The HTTP2 connection window size that the client can accept in bytes. | ||
| Stream Window Size | The HTTP2 stream window size that the client can accept in bytes. | ||
| Send WINDOW_UPDATE when remaining window size below |
Sends a WINDOW_UPDATE frame when the remaining window size that the server can accept is below the specified number of bytes.
|
||
| Allow Server Push |
Select to allow the server to send additional resources to the client, before the client requests them. If deselected, the server sends resources only upon client request.
|
||
| Server Profile | |||
| Protocol Level |
In proxy mode, we can choose HTTP1.1 or HTTP/2 for server side.
|
||
| Max Data Frame Size | The maximum DATA frame payload size that the server can send in bytes. | ||
| Max Concurrent Streams per Connection | The maximum concurrent streams per connection that the server allows the DUT (device under test) to create. | ||
| Override Flow Control | Select to enable the HTTP2 flow control fields, Connection Window Size, Stream Window Size, and Send WINDOW_UPDATE. | ||
| Connection Window Size | The HTTP2 connection window size that the server can accept in bytes. | ||
| Stream Window Size | The HTTP2 stream window size that the server can accept in bytes. | ||
|
Send WINDOW_UPDATE when remaining window size below |
Sends a WINDOW_UPDATE frame when the remaining window size that the client can accept is below the specified number of bytes.
|
||