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:

1. In Performance testing, expand HTTP/2 and click CC.
2. Click Create New.
3. Configure the network or select a network template. See Using network configuration templates for how to create a network template.
4. Select a Certificate Group, if applicable.
5. Click OK.
6. Configure the test case options described below.
7. 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 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 CC test case options

For details about the common options for HTTP/2 cases, see HTTP/2 test case common options.

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. This value should be smaller than Connection Window Size and Stream Window Size.
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. Allow Server Push only exist in Specifics->Client.
Server Profile
Protocol Level	In proxy mode, we can choose HTTP1.1 or HTTP/2 for server side. HTTP1.1: This means DUT will convert HTTP/2 traffic to HTTP1.1 and forward it to the server. HTTP/2: This means the backend server supports HTTP/2.
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. This value should be smaller than Connection Window Size and Stream Window Size.