<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Reverse Proxy on Remko's Blog</title><link>https://remkoweijnen.nl/blog/tags/reverse-proxy/</link><description>Recent content in Reverse Proxy on Remko's Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 10 Feb 2017 14:10:45 +0000</lastBuildDate><atom:link href="https://remkoweijnen.nl/blog/tags/reverse-proxy/index.xml" rel="self" type="application/rss+xml"/><item><title>Show Client IP Address when using NetScaler as a Reverse Proxy</title><link>https://remkoweijnen.nl/blog/2017/02/10/show-client-ip-address-when-using-netscaler-as-a-reverse-proxy/</link><pubDate>Fri, 10 Feb 2017 14:10:45 +0000</pubDate><guid>https://remkoweijnen.nl/blog/2017/02/10/show-client-ip-address-when-using-netscaler-as-a-reverse-proxy/</guid><description>&lt;p&gt;&lt;a href="https://remkoweijnen.nl/blog/wp-content/uploads/2017/02/image-3.webp" class="glightbox" data-type="image" data-gallery="post-3963"&gt;&lt;img loading="lazy" decoding="async" style="float: right; display: inline;" title="Citrix NetScaler" src="https://remkoweijnen.nl/blog/wp-content/uploads/2017/02/image_thumb-3.webp" alt="Citrix NetScaler Logo" width="144" height="77" align="right" /&gt;&lt;/a&gt;Recently I switched over my blog from a hoster to a self hosted VM. In my setup I am using Citrix NetScaler as a reverse proxy.&lt;/p&gt;
&lt;p&gt;Simular to when you&amp;rsquo;re using a 3rd party reverse proxy such as &lt;a href="https://www.cloudflare.com/"&gt;CloudFlare&lt;/a&gt; you will see the IP address from the reverse proxy instead of the actual Client IP Address on your webserver.&lt;/p&gt;
&lt;p&gt;This means that your logging will all show the same, internal, IP address and that IP Based Access Rules will not work.&lt;/p&gt;
&lt;p&gt;Fortunately this is easy to solve by having NetScaler add the Client IP Address in the headers and rewriting the address on your webserver.&lt;/p&gt;</description></item></channel></rss>