<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Not able to log XFF (Actual Client IP) in PaloAlto Logs even when we enable XFF and URL filtering profile in Palo's in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/not-able-to-log-xff-actual-client-ip-in-paloalto-logs-even-when/m-p/1253286#M6883</link>
    <description>&lt;P&gt;I've got the same issue. Been doing test and with decrypt ON, I cant see XFF header. Without decrypt, works OK.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Dont know what the issue can be &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 29 Apr 2026 14:35:51 GMT</pubDate>
    <dc:creator>ricardomo</dc:creator>
    <dc:date>2026-04-29T14:35:51Z</dc:date>
    <item>
      <title>Not able to log XFF (Actual Client IP) in PaloAlto Logs even when we enable XFF and URL filtering profile in Palo's</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/not-able-to-log-xff-actual-client-ip-in-paloalto-logs-even-when/m-p/1242643#M6487</link>
      <description>&lt;P&gt;Issue Summary – XFF Not Logged on Palo Alto (Even With Decryption ON)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are running a flow where AWS ALB inserts X-Forwarded-For (XFF) and the Palo Alto firewall performs SSL decryption + re-encryption:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Flow:&lt;/P&gt;&lt;P&gt;Client --&amp;gt; Internet --&amp;gt; AWS ALB (HTTPS) (Palo's are registered as TG IP) --&amp;gt; Palo Alto FW (SSL Decrypt) --&amp;gt; Server&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What works&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;ALB is configured to append XFF.&lt;/LI&gt;&lt;LI&gt;Server (Nginx) correctly logs the XFF header.&lt;/LI&gt;&lt;LI&gt;SSL decryption on Palo Alto is working → Traffic log shows “Decrypted: yes”.&lt;/LI&gt;&lt;LI&gt;Application is identified as web-browsing (so HTTP parsing should work).&lt;/LI&gt;&lt;LI&gt;Firewall-stage PCAP for HTTP/80 clearly shows X-Forwarded-For header.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What doesn’t work&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;For HTTPS/443 traffic, even though decryption succeeds, XFF does NOT appear in:&lt;/LI&gt;&lt;LI&gt;Traffic logs (X-Forwarded-For column is empty)&lt;/LI&gt;&lt;LI&gt;Firewall-stage decrypted PCAP (XFF is missing for decrypted 443 sessions)&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What we tested&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Confirmed ALB → Palo traffic on port 443 is decrypted (Decrypted: yes).&lt;/LI&gt;&lt;LI&gt;Verified that HTTP/80 decrypted traffic shows XFF in PCAP.&lt;/LI&gt;&lt;LI&gt;Verified that HTTPS/443 decrypted traffic does NOT show XFF in PCAP.&lt;/LI&gt;&lt;LI&gt;Confirmed Global Content-ID setting:&lt;/LI&gt;&lt;/OL&gt;&lt;UL&gt;&lt;LI&gt;“Use X-Forwarded-For Header: Enabled for Security Policy.”&lt;/LI&gt;&lt;/UL&gt;&lt;OL&gt;&lt;LI&gt;Verified security rule logging is enabled and URL filtering profile applied.&lt;/LI&gt;&lt;LI&gt;Confirmed no packet capture setting is blocking XFF logging.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Observed Behavior&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;XFF header is present on HTTP/80 after Palo decrypt → Visible in PCAP.&lt;/LI&gt;&lt;LI&gt;XFF header is missing on HTTPS/443 after Palo decrypt → Not visible in PCAP.&lt;/LI&gt;&lt;LI&gt;Therefore: Firewall cannot log XFF because the header never arrives on the decrypted HTTPS session.&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Wed, 26 Nov 2025 08:46:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/not-able-to-log-xff-actual-client-ip-in-paloalto-logs-even-when/m-p/1242643#M6487</guid>
      <dc:creator>tn001140351</dc:creator>
      <dc:date>2025-11-26T08:46:30Z</dc:date>
    </item>
    <item>
      <title>Re: Not able to log XFF (Actual Client IP) in PaloAlto Logs even when we enable XFF and URL filtering profile in Palo's</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/not-able-to-log-xff-actual-client-ip-in-paloalto-logs-even-when/m-p/1242735#M6489</link>
      <description>&lt;P&gt;Do we have any solution for this issue?&lt;/P&gt;</description>
      <pubDate>Thu, 27 Nov 2025 14:56:02 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/not-able-to-log-xff-actual-client-ip-in-paloalto-logs-even-when/m-p/1242735#M6489</guid>
      <dc:creator>tn001140351</dc:creator>
      <dc:date>2025-11-27T14:56:02Z</dc:date>
    </item>
    <item>
      <title>Re: Not able to log XFF (Actual Client IP) in PaloAlto Logs even when we enable XFF and URL filtering profile in Palo's</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/not-able-to-log-xff-actual-client-ip-in-paloalto-logs-even-when/m-p/1253286#M6883</link>
      <description>&lt;P&gt;I've got the same issue. Been doing test and with decrypt ON, I cant see XFF header. Without decrypt, works OK.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Dont know what the issue can be &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 29 Apr 2026 14:35:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/not-able-to-log-xff-actual-client-ip-in-paloalto-logs-even-when/m-p/1253286#M6883</guid>
      <dc:creator>ricardomo</dc:creator>
      <dc:date>2026-04-29T14:35:51Z</dc:date>
    </item>
  </channel>
</rss>

