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

# sk183743 - URLs in a custom application site are not matched

| Property | Value |
|----------|-------|
| Solution ID | sk183743 |
| Date Created | 2025-08-07 |
| Last Modified | 2025-09-01 |
| Technical Level | General |
| Products | Security Gateway |
| Versions | R82, R81.20 |

## Symptoms

- * A Security Gateway version R81.20 and higher does not match URLs in a custom application site when the custom application is configured with a category, and the category is used in the rule base, not the custom application.

* If the custom application site is referenced anywhere in the policy, URL matching via category begins working..

## Cause

Check Point R81.20 introduced a feature called Partial Load, which optimizes policy installation by loading only relevant objects. If a custom application site is not explicitly used in the policy, its URLs will not be matched - even if its category is used.

## Solution

**Warning**: Registry changes can affect system behavior. Always back up your configuration before proceeding.

To restore previous behavior, disable Partial Load on the Management Server.

* Disable Partial load:

  `ckp_regedit -a SOFTWARE/CheckPoint/FW1 APPI_PARTIAL_LOAD_MODE 0`
* To enable Partial load:

  `ckp_regedit -a SOFTWARE/CheckPoint/FW1 APPI_PARTIAL_LOAD_MODE 1`
* To verify the current registry setting, run:

  `ckp_regedit SOFTWARE/CheckPoint/FW1 APPI_PARTIAL_LOAD_MODE`

For the change to take effect, after enabling / disabling the feature, restart Check Point services on the Security Gateway:  
`# cpstop ; cpstart`

Best Practice: Test changes in a lab environment before applying to production.  
**If the issue persists:** Show/Hide Section  
Check if the policy installation uses Partial Load:

1. Run a light policy debug:

   `# TDERROR_ALL_policy=5 fw fetchlocal -d $FWDIR/state/__tmp/FW1/ >& fetch.txt`
2. Open fetch.txt and search for these lines:

   ```
     [50156 3930059200]appi_cmi_get_appi_mode: called
     [50156 3930059200]appi_cmi_get_appi_load_mode_from_registry: called
     [50156 3930059200]appi_cmi_get_appi_load_mode_from_registry: g_appi_load_mode is set to: E_APPI_LOAD_ALL
     [50156 3930059200]appi_cmi_get_appi_mode: g_appi_load_mode is set to: E_APPI_LOAD_PARTIAL
     
   ```

If `E_APPI_LOAD_PARTIAL` appears even though the registry key is set to load all:  

[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).

<br />

---

# 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