<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Mod_authz_host on Nico Maas</title>
        <link>https://www.nico-maas.de/tags/mod_authz_host/</link>
        <description>Recent content in Mod_authz_host on Nico Maas</description>
        <generator>Hugo -- gohugo.io</generator>
        <language>en-us</language>
        <lastBuildDate>Mon, 12 Sep 2016 10:36:40 +0000</lastBuildDate><atom:link href="https://www.nico-maas.de/tags/mod_authz_host/index.xml" rel="self" type="application/rss+xml" /><item>
            <title>[Ubuntu] Secure your Apache 2 Reverse Proxy</title>
            <link>https://www.nico-maas.de/posts/2016-09-12-ubuntu-secure-your-apache-2-reverse-proxy/</link>
            <pubDate>Mon, 12 Sep 2016 10:36:40 +0000</pubDate>
            <guid>https://www.nico-maas.de/posts/2016-09-12-ubuntu-secure-your-apache-2-reverse-proxy/</guid>
            <description>&lt;p&gt;We got an Apache 2, working as Reverse Proxy to some Docker instances (we won&amp;rsquo;t talk about the nginx vs Apache stuff here for the same reasons we won&amp;rsquo;t talk about vi vs emacs vs xyz ;)) - and somehow we realized that our apps are a little bit too sensitive to allow them from any ip.&lt;/p&gt;&#xA;&lt;p&gt;First, we want to activate the needed modules. Normally that should not be necessary, but for sake of completeness:&lt;/p&gt;</description>
        </item></channel>
</rss>
