/cfg/slb/accel/http2/http2pol <policy ID (alphanumeric)>
HTTP2 Policy Menu
Use this menu to configure HTTP/2 policy parameters.
Note: When HTTP/2 Full Proxy is enabled, the HTTP/2 Gateway becomes disabled.
The latest versions of most Web browsers support HTTP/2, which is enabled by default. To gain the performance improvement value of HTTP/2 without changing your back-end systems, Alteon provides a high speed gateway from HTTP/2 to HTTP/1. Your back-end system can remain intact while any browsers that are HTTP/2-ready can benefit from HTTP/2 right away.
To benefit the most from the single optimized TCP connection between client and server with HTTP/2:

Alteon should be the HTTP/2 terminating device. It is best if the long haul is between the client side of the connection and Alteon.
— It is best that a service use a single front-end IP address. A service that uses multiple front‑end IP addresses (for example for www.site.com and for anotherdomain.site.com, for different resources or a different part of the page) would require multiple connection establishments.
— HTTP/2 can be used only for HTTPS services (not for filters).
— Radware recommends that you use HTTP/2 in conjunction with multiplexing to back-end servers, compression, and caching. To add acceleration value, work with FastView to best leverage HTTP/2 FastView PUSH. FastView PUSH support is included both with FastView and with FastView+ for Alteon NG.

HTTP/2 implies that the site is available and used over SSL. If your site is currently using clear text HTTP, you may benefit from the following Alteon capabilities for the transition to HTTPS:
— Make sure that the SSL Policy Convert parameter is set to Enabled.
— Add header modification for front-end-SSL to indicate to the back-end system to use links to HTTPS.
Notes

The SSL policy used in conjunction with the HTTP/2 Gateway must ensure that TLS 1.2 or later is enabled and the selected Cipher Suite includes AES-GCM ciphers. The allowed versions and cipher suite of the default SSL policy fulfill this requirement.

Radware recommends for HTTP/2 services that you set
/cfg/slb/virt/service/http/connmgt either to
enabled, or if client IP visibility is required on the servers, to
h2.

HTTP/2 is not supported in conjunction with APM.

The HTTP/2 Gateway is currently not supported in conjunction with Pass SSL Info to back-end servers and with Pass Client Authentication Information to back-end servers.
[HTTP2 Policy <policy ID> Menu] name - Set descriptive HTTP2 policy name backend - Backend Menu streams - Set maximum concurrent streams per connection hpack - Set header compression table size header - Set header insertion to indicate frontend uses HTTP2 ena - Enable HTTP2 policy dis - Disable HTTP2 policy del - Delete HTTP2 policy cur - Display current HTTP2 policy configuration |
HTTP2 Policy Menu
Command Syntax and Usage |
---|
name <name>|none |
| Sets the HTTP/2 policy name. Values: 0–32 alphanumeric characters |
backend |
| |
streams <1-128> |
| Specifies the maximum number of concurrent requests allowed to be outstanding on a single HTTP/2 connection. This is the maximum number of concurrent back-end connections per client. Values: 1-128 Default: 10 |
hpack [small|medium|large] |
| Specifies the size of the header table per connection. The HTTP/2 protocol compresses HTTP headers to save bandwidth. A larger table size enables better compression, but requires more memory. A smaller table size enables more efficient memory usage. Values: small (4 KB), medium (8 KB), large (16 KB) Default: Medium |
header |
| Specifies whether an HTTP header that indicates that HTTP/2 is being used is inserted into the request sent to the origin Web server. The header is inserted only when the front-end client connections uses HTTP/2. Note: This command is relevant only when configuring HTTP/2 policy settings for the HTTP/2 Gateway. It is not required when configuring HTTP/2 policy settings for Full Proxy. Values:  e (enabled) — When you enable insertion of an HTTP header, you are prompted to set a new header name. To indicate to the back-end server that the front-end is using HTTP/2, enter the header name followed by a “:” (colon), followed by a single space, and followed by the value as required in your environment. Default value: X-HTTP2: on Note: For the default value, a space is required between the colon and the string “on”. If you specify this value within a CLI path, you must include quotation marks. For example: /cfg/slb/accel/http2/http2pol <name>/header ena “X-HTTP2: on”  d (disabled) Maximum characters: 128 Default: d |
ena |
| Enables an HTTP/2 policy. The HTTP/2 policy is enabled by default. |
dis |
| Disables an HTTP/2 policy. The HTTP/2 policy is enabled by default. |
del |
| Deletes an HTTP/2 policy. |
cur |
| Displays the current HTTP/2 configuration. |