- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Enhanced Security Measures in Place: To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.
07-06-2022 08:14 PM
what`s mean below article?
For non-URL Filtering logs, XFF IP logging is supported only when packet capture is not enabled.
-->> It mean that XFF ip is visible only when packet capture is not enable in other logs setting ?
The X-Forwarded-For IP column does not display a value if the firewall detects a threat that requires a reset action (reset-client, reset-server, or reset-both
-->> This mean that threat logs other than reset are shown?
04-11-2023 08:55 PM
For non-URL Filtering logs, XFF IP logging is supported only when packet capture is not enabled.
-->> It mean that XFF ip is visible only when packet capture is not enable in other logs setting ?---yes
The X-Forwarded-For IP column does not display a value if the firewall detects a threat that requires a reset action (reset-client, reset-server, or reset-both
-->> This mean as once firewall detects any threat with action "reset", the decoder will stop decoding further packet. If the XFF field does not reside in the last packet, we have no way to parse it. However if XFF field already reside in the last packet, then you are still able to see it. That's why for reset action there still might be a chance to see the value on the X-Forwarded-For IP column.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!