Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Products Best Practices Hardware Guides Products A-Z
Summary
By Solution
By 4D Pillars
By Cloud
Secure Networking
Unified SASE
Security Operations
Secure SD-WAN
Secure Access Service Edge (SASE)
ZTNA
LAN Edge
Identity and Access Management
Next Generation Firewall
Public Cloud
Private Cloud
FortiCloud
Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
    • More >>
    Unified SASE
  • Single Vendor SASE
  • Cloud Network Security
  • Secure Endpoint Connectivity
  • Web Application / API Protection
    • More >>
    Security Operations
  • Security Operations Automation
  • Identity
  • Early Detection & Prevention
    • More >>
    Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
  • Communication & Surveillance
    • Unified SASE
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Cloud Network Security
  • Cloud-Native Security
  • Web Application / API Protection
    • Security Operations
  • Security Operations Automation
  • Endpoint
  • Data Protection
  • Identity
  • Email
  • Early Detection & Prevention
  • Expert Services
  • Edge Firewall
  • Orchestration & management
  • SD Branch
  • Application Delivery
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Secure Private Access
  • Thin Edge
  • Identity
  • Application Gateway
  • Enterprise Asset Management
  • Endpoint Agent
  • Agentless Security Posture
  • Identity
  • Wireless
  • Switching
  • Identity
  • Privilege Acccess Management
  • Next Generation Firewall
  • Orchestration & management
  • Expert Services
  • All
  • All
  • Account Management
  • SAAS Management
  • SAAS Application Security
  • Managed Services
  • Platform as a service (PAAS)
  • Other SAAS Services
    • 4D Resources
    Solution Hubs
  • 4D Pillars
  • Cloud
  • Popular Solutions

    • Handbook

    Home FortiADC 7.4.4 Handbook
    7.4.4
    7.4.5
    7.4.4
    7.4.3
    7.4.2
    7.4.1
    7.4.0
    7.2.7
    7.2.6
    7.2.5
    7.2.4
    7.2.3
    7.2.2
    7.2.1
    7.2.0
    7.1.4
    7.1.3
    7.1.2
    7.1.1
    7.1.0
    7.0.5
    7.0.4
    7.0.3
    7.0.2
    7.0.1
    7.0.0
    6.2.6
    6.2.5
    6.2.4
    6.2.3
    6.2.2
    6.2.1
    6.2.0
    6.1.6
    6.1.5
    6.1.4
    6.1.3
    6.1.2
    6.1.1
    6.1.0
    6.0.1
    6.0.0
    5.4.3
    5.4.2
    5.4.1
    5.4.0
    5.3.6
    5.3.5
    5.3.4
    5.3.3
    5.3.2
    5.3.1
    5.3.0
    5.2.7

    Configuring HTTP2 profiles

    Configuring HTTP2 profiles

    You can now create application profiles that support HTTP2. To do so, you must first create an HTTP2 Profile, then use that profile when creating a new application profile.

    To configure HTTP2 profiles:
    1. Go to Server Load Balance > Application Resources.
    2. Click the HTTP2 Profile tab.
    3. Click Create New to display the configuration editor.
    4. Complete the configuration as described in HTTP2 profile configuration guidelines.
    5. Save the configuration.

    HTTP2 profile configuration guidelines
    Type Profile Configuration Guidelines

    Name

    Specify a unique name for the HTTP2 profile.

    Priority Mode

    Set to Best Effort. Not configurable.
    Upgrade Mode Set to Upgradeable. Not configurable.
    Max Concurrent Stream Specify the maximum number of concurrent streams available at one time. The default number is 5.
    Max Receive Window Specify the maximum number of bytes that can be received without sending an acknowledgment response. The default is 65535 bytes.
    Max Frame Size Specify the max size of the data frames, in bytes that the HTTP2 protocol sends to the client. Setting a large frame size improves network utilization, but it can also affect concurrency. The default is 16384 bytes.
    Header Table Size Specify the size of the header table, in KB. A larger table size allows for better HTTP header compression, but it requires more memory. The default is 4096.
    Header List Limitation Specify the size of the name value length , in bytes, that the HTTP2 protocol sends in a single header frame. The default is 65536.
    SSL Constraint

    Enable or disable SSL constraint. If enabled, the following conditions must be met:

    • The TLS implementation supports Server Name Indication.
    • The TLS implementation disables compression.
    • The TLS implementation disables renegotiation.
    • Renegotiation takes place before the connection preface is sent.
    • HTTP/2 uses cipher suites with ephemeral key exchange.
    • Ephemeral key exchange has a size of at least 2048 bits (for DHE) or a security level of at least 128 bits (for ECDHE).
    • Clients accept DHE no smaller than 4096 bits.
    • Stream or block ciphers are not used with HTTP.
    Previous
    Next

    Configuring HTTP2 profiles

    Configuring HTTP2 profiles

    You can now create application profiles that support HTTP2. To do so, you must first create an HTTP2 Profile, then use that profile when creating a new application profile.

    To configure HTTP2 profiles:
    1. Go to Server Load Balance > Application Resources.
    2. Click the HTTP2 Profile tab.
    3. Click Create New to display the configuration editor.
    4. Complete the configuration as described in HTTP2 profile configuration guidelines.
    5. Save the configuration.

    HTTP2 profile configuration guidelines
    Type Profile Configuration Guidelines

    Name

    Specify a unique name for the HTTP2 profile.

    Priority Mode

    Set to Best Effort. Not configurable.
    Upgrade Mode Set to Upgradeable. Not configurable.
    Max Concurrent Stream Specify the maximum number of concurrent streams available at one time. The default number is 5.
    Max Receive Window Specify the maximum number of bytes that can be received without sending an acknowledgment response. The default is 65535 bytes.
    Max Frame Size Specify the max size of the data frames, in bytes that the HTTP2 protocol sends to the client. Setting a large frame size improves network utilization, but it can also affect concurrency. The default is 16384 bytes.
    Header Table Size Specify the size of the header table, in KB. A larger table size allows for better HTTP header compression, but it requires more memory. The default is 4096.
    Header List Limitation Specify the size of the name value length , in bytes, that the HTTP2 protocol sends in a single header frame. The default is 65536.
    SSL Constraint

    Enable or disable SSL constraint. If enabled, the following conditions must be met:

    • The TLS implementation supports Server Name Indication.
    • The TLS implementation disables compression.
    • The TLS implementation disables renegotiation.
    • Renegotiation takes place before the connection preface is sent.
    • HTTP/2 uses cipher suites with ephemeral key exchange.
    • Ephemeral key exchange has a size of at least 2048 bits (for DHE) or a security level of at least 128 bits (for ECDHE).
    • Clients accept DHE no smaller than 4096 bits.
    • Stream or block ciphers are not used with HTTP.
    Previous
    Next