Updated Date: 07/07/2026
Create a custom HTTP/2 profile
Part of creating an HTTP/2 full-proxy configuration is to create an HTTP/2 profile that you can use for both client-side and server-side application traffic. When you assign the profile to a virtual server, the BIG-IP system applies the settings in the profile to the traffic.
Note: For the most expedient HTTP/2 full-proxy configuration, you can create a single HTTP/2 profile that the BIG-IP system will apply to both client-side and server-side HTTP/2 traffic. Alternatively, if you want the BIG-IP system to manage client-side and server-side traffic in different ways, you can create two separate HTTP/2 profiles and configure the settings differently in each profile.
-
On the Main tab, click Local Traffic > Profiles > Services > HTTP/2.
-
Click Create.
-
Type a Name for the profile, such as
my_http2_profile. -
For the Parent Profile setting, retain the default value
http2, or select a different profile.This setting specifies the profile that you want to use as the parent profile. Your new profile inherits all settings and values from the parent profile that you select.
-
From the Settings list, you can select Advanced to view the advanced settings.
This setting is optional, depending on the settings you want to configure.
-
On the far-right side of the screen, select the Custom check box.
-
In the Concurrent Streams Per Connection field, retain or change the numeric value.
This setting specifies how many concurrent requests are allowed to be outstanding on a single HTTP/2 connection.
-
In the Connection Idle Timeout field, retain or change the numeric value.
This setting specifies the number of seconds that a connection is idle before the connection is eligible for deletion.
-
From the Insert Header list, retain the default value of Disabled, or select Enabled.
This setting specifies whether the BIG-IP system should add an HTTP header to the HTTP request to show that the request was received over HTTP/2.
-
In the Insert Header Name field, retain the default value or, if the Insert Header setting is enabled, change the header name.
This setting specifies the name of the header that the BIG-IP system will add to the HTTP request when the Insert Header is enabled.
-
From the Enforce TLS Requirements list, ensure that Enabled. is selected.
Important: Enforcing TLS requirements is required for successful HTTP/2 full-proxy deployment.
-
Forthe Activation Modes setting, retain the default value of ALPN (Application Layer Protocol Negotiation) or select Always.
This setting specifies the condition that will cause the BIG-IP system to handle an incoming connection as an HTTP/2 connection.
-
In the Frame Size field, retain the default value of 2048, or change the value.
This setting specifies the size, in bytes, of the data frames that HTTP/2 will produce.
-
In the Receive Window field, retain the default numeric value of 32, or change the numeric value.
This setting specifies, in kilobytes, the size of the receive window for HTTP/2 flow-control.
-
In the Write Size field, retain the default numeric value of 16384, or change the numeric value.
This setting specifies the size, in bytes, of the SSL records that HTTP/2 will produce.
-
In the Header Table Size field, retain the default numeric value of 4096, or change the numeric value.
This setting specifies the table size that the BIG-IP system will use for the compression of headers (unused).
-
If you want the BIG-IP system to manage server-side traffic differently from client-side traffic, click Repeat and create another HTTP/2 profile.
-
Click Finished.
Any custom HTTP/2 profile that you have created now appears on the HTTP/2 profile list screen and is ready for you to assign to a virtual server.