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

# sk111016 - The "X-Forward-For" (XFF) header is not stripped from web traffic when Security Gateway is configured as HTTP/HTTPS Proxy in Non Transparent mode

| Property | Value |
|----------|-------|
| Solution ID | sk111016 |
| Date Created | 2016-04-14 |
| Last Modified | 2017-03-20 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |

## Symptoms

- * The "X-Forward-For" (XFF) header is not stripped from web traffic (internal client IP address is revealed to Internet) by Security Gateway in the following scenario:

  * Example topology:  
    Client -\> Squid Proxy (using CP GW as next proxy) -\> CP GW (configured as Non Transparent Proxy) -\> Internet
  * Security Gateway is configured as HTTP/HTTPS Proxy in Non Transparent mode:  
    Security Gateway object - HTTP/HTTPS Proxy pane - Advanced
  "X-Forward-For header (original client source IP address)" box is checked in:  
  Security Gateway object - HTTP/HTTPS Proxy pane - Advanced
  * Identity Awareness blade is enabled
* Disabling HTTP/HTTPS Proxy on Security Gateway resolves the issue (the XFF header is stripped correctly).

## 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