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

# sk120360 - The XFF header (X-Forward-For) is not added to web traffic when Security Gateway is in Transparent Mode

| Property | Value |
|----------|-------|
| Solution ID | sk120360 |
| Date Created | 2017-10-09 |
| Last Modified | 2019-11-22 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |
| OS | Gaia |

## Symptoms

- * HTTP/HTTPS transparent proxy is enabled on the Security gateway with the XFF header option enabled, but the next hop device cannot see the XFF header attached.
* Debugs on the gateway (`fw ctl debug -m fw + conn drop packet packval` and `fw ctl debug -m WS + all`) shows:   

  `
  [cpu_X];[fwY_Z];###:{module} fw_http_proxy_inspection: not internal interface X.X.X.X not match to proxy;`

## Cause

Incoming interface for web traffic is not defined as "internal", which makes the traffic uneligible for the XFF header.

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# 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