# Custom Applications with Spaces Are Not Enforced in HTTPS Inspection Rulebase

**Product**: HTTPS Inspection  
**Version**: R81.20, R82, R82.10  
**Last Modified**: 2026-07-23

## Symptoms

- An HTTPS Inspection rule that contains a custom application whose name includes spaces or certain unsupported characters does not match during policy enforcement.
- After you rename the custom application to remove spaces and reinstall the policy, the rule matches as expected.

## Cause

Within HTTPS Inspection processing, certain object name patterns - specifically names containing whitespace or service‑like textual components - may be internally normalized into a unique ID format (V{UID} pattern) on the Management Server.

This behavior applies only to the HTTPS Inspection rulebase and does not affect the Access Control rulebase.

## Solution

This problem was fixed. The fix is included in:

- [Jumbo Hotfix Accumulator for R82.10](https://sc1.checkpoint.com/documents/Jumbo_HFA/R82.10/Default.htm) starting from Take 36

If you choose not to upgrade, Check Point can supply a **Hotfix**. [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 the Hotfix.

For faster resolution and verification, please collect [CPinfo files](http://supportcontent.checkpoint.com/solutions?id=sk92739) from the Security Management Server and Security Gateways involved in the case.

**Hotfix installation instructions:**

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

#### NOTE

This solution has been verified for the specific scenario, described by the combination of Product, Version and Symptoms. It may not work in other scenarios.