> Source: [sk184955](https://support.checkpoint.com/results/sk/sk184955)

# sk184955 - HTTPS Inspection with HyperFlow causes HTTP parsing errors and blocked HTTPS Traffic

| Property | Value |
|----------|-------|
| Solution ID | sk184955 |
| Date Created | 2026-05-19 |
| Last Modified | 2026-05-22 |
| Technical Level | General |
| Products | Security Gateway |
| Versions | R81.20 |

## Symptoms

- * When HTTPS Inspection is enabled on a Quantum Security Gateway, end users may not reliably access some HTTPS websites.
* Observed behavior includes:
  * Some HTTPS sites load as blank (white) pages.
  * Other sites load very slowly or fail to load completely.
  * The same sites work normally when HTTPS Inspection is bypassed or disabled.
* Security logs for the affected connections show blocked traffic with HTTP parsing errors, for example:
  *

    ```
    Blade: Application Control
    Action: Block
    Reason: Application Control - HTTP parsing error occurred (2)
    Precise Error: unknown error
    ```

  *

    ```
    Precise Error: malformed protocol name in request
    ```

* Disabling HyperFlow (connection pipelining) on the Security Gateway allows most affected HTTPS traffic to work normally again. Disabling HTTP/2 inspection for testing changes the behavior but does not fully eliminate the parsing errors while HyperFlow remains enabled.

## Cause

This behavior occurs on Check Point Security Gateways running R81.20 with Jumbo Hotfix Accumulator takes earlier than Take 122, under these conditions:

* HTTPS Inspection is enabled and traffic is decrypted.
* Some HTTPS connections negotiate HTTP/2 with HTTP/1.1 fallback using ALPN.
* HyperFlow distributes inspected HTTPS flows across multiple CoreXL instances.

Under these combined conditions, a specific HTTP parsing path in the Application Control and HTTPS Inspection engines may incorrectly classify valid HTTP traffic as malformed. When this occurs, the engine enforces its default handling for parsing errors and blocks the affected connections.

## Solution

[Contact Check Point Support](https://www.checkpoint.com/support-services/contact-support/) to get a Hotfix for this issue.

A Support Engineer will make sure the Hotfix is compatible with your environment before providing it.  
For faster resolution and verification, collect these files:

1. [CPinfo](https://support.checkpoint.com/results/sk/sk92739) file from the Management Server involved in the case.
2. [CPinfo](https://support.checkpoint.com/results/sk/sk92739) file from the Security Gateway / each Cluster Member / Security Group involved in the case.

**Hotfix installation instructions:**   
Refer to [sk168597 - How to install a Hotfix](https://support.checkpoint.com/results/sk/sk168597).

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content