<?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: x-forwarded-for in user sessions in Real User Monitoring</title>
    <link>https://community.dynatrace.com/t5/Real-User-Monitoring/x-forwarded-for-in-user-sessions/m-p/110941#M849</link>
    <description>&lt;P&gt;Hi Henk, &lt;/P&gt;&lt;P&gt;For Applications, you can find the settings used under Settings &amp;gt; Web and mobile monitoring &amp;gt; IP determination. Dynatrace uses a few widely used headers to extract the true cient IP address. However, your application may use a custom header for tracing the original client IP. You can add that header in this settings page. Alternatively, there may be a config issue where the load balancer actually strips any header that carries the original client IP and as such this behaviour needs to be corrected at the LB level.&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.dynatrace.com/legacyfs/online/24430-1585736784792.png" /&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Radu&lt;/P&gt;</description>
    <pubDate>Wed, 01 Apr 2020 10:26:37 GMT</pubDate>
    <dc:creator>Radu</dc:creator>
    <dc:date>2020-04-01T10:26:37Z</dc:date>
    <item>
      <title>x-forwarded-for in user sessions</title>
      <link>https://community.dynatrace.com/t5/Real-User-Monitoring/x-forwarded-for-in-user-sessions/m-p/110940#M848</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I assume the x-forwarded-for works for services, but in the application not and everybody gets the ipaddress of the loadbalancer? &lt;/P&gt;&lt;P&gt;KR Henk&lt;/P&gt;</description>
      <pubDate>Wed, 01 Apr 2020 10:07:43 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Real-User-Monitoring/x-forwarded-for-in-user-sessions/m-p/110940#M848</guid>
      <dc:creator>henk_stobbe</dc:creator>
      <dc:date>2020-04-01T10:07:43Z</dc:date>
    </item>
    <item>
      <title>Re: x-forwarded-for in user sessions</title>
      <link>https://community.dynatrace.com/t5/Real-User-Monitoring/x-forwarded-for-in-user-sessions/m-p/110941#M849</link>
      <description>&lt;P&gt;Hi Henk, &lt;/P&gt;&lt;P&gt;For Applications, you can find the settings used under Settings &amp;gt; Web and mobile monitoring &amp;gt; IP determination. Dynatrace uses a few widely used headers to extract the true cient IP address. However, your application may use a custom header for tracing the original client IP. You can add that header in this settings page. Alternatively, there may be a config issue where the load balancer actually strips any header that carries the original client IP and as such this behaviour needs to be corrected at the LB level.&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.dynatrace.com/legacyfs/online/24430-1585736784792.png" /&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Radu&lt;/P&gt;</description>
      <pubDate>Wed, 01 Apr 2020 10:26:37 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Real-User-Monitoring/x-forwarded-for-in-user-sessions/m-p/110941#M849</guid>
      <dc:creator>Radu</dc:creator>
      <dc:date>2020-04-01T10:26:37Z</dc:date>
    </item>
  </channel>
</rss>

