<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>X-Forwarded-For on sys-dev.cat</title>
    <link>https://www.sys-dev.cat/categories/x-forwarded-for/</link>
    <description>Recent content in X-Forwarded-For on sys-dev.cat</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Sat, 10 Mar 2018 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.sys-dev.cat/categories/x-forwarded-for/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Restoring original visitor ip with Cloudflare and Nginx</title>
      <link>https://www.sys-dev.cat/blog/5/</link>
      <pubDate>Sat, 10 Mar 2018 00:00:00 +0000</pubDate>
      
      <guid>https://www.sys-dev.cat/blog/5/</guid>
      <description>Who doesn&amp;rsquo;t know Cloudflare yet? Cloudflare is one of the most used CDN (Content Delivery Network) providers in the world.
Using a CDN in front of your tipical web server (For example nginx) provides a lot of advantages, like lower response times, increased security by hiding your real server ip address, and in the case of Cloudflare a lot of different features. On the other hand since Cloudflare acts as a reverse proxy some of your apps (Log analyzers, or any other kind of app that requires your visitors ip addresses) might stop working at all since your server won&amp;rsquo;t be able to get the real ip addresses of your visitors anymore.</description>
    </item>
    
  </channel>
</rss>