The information you are about to copy is INTERNAL!
DO NOT share it with anyone outside Check Point.
HTTPS Inspection and 'X-Forward-For' (XFF) HTTP header when inspecting proxy traffic
| Solution ID |
sk92839 |
| Product |
HTTPS Inspection |
| Version |
R75.40, R75.40VS, R75.45, R75.46, R75.47, R76, R77, R77.10, R77.20, R77.30, R80.10, R80.20, R80.30 |
| OS |
Gaia, SecurePlatform 2.6, Crossbeam XOS, IPSO 6.2 |
| Platform / Model |
All |
| Date Created |
19-May-2013
|
| Last Modified |
12-Feb-2020
|
Symptoms
- Application Control and URL Filtering Blades cannot use the '
X-Forward-For header' Proxy configuration option when working on HTTPS traffic via HTTPS Inspection (SmartDashboard - Check Point Security Gateway object - 'Identity Awareness' pane - section 'Proxy Support for Application Control and URL Filtering Blades').
Cause
Since the traffic from the Client is encrypted, it is impossible for the Proxy to modify it and add X-Forward-For header.
Solution
|
Note: To view this solution you need to
Sign In
.
|
