<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>varnish on {bjørn:johansen}</title>
    <link>https://bjornjohansen.com/tag/varnish/</link>
    <description>Recent content in varnish on {bjørn:johansen}</description>
    <generator>Hugo -- 0.118.2</generator>
    <language>en-US</language>
    <lastBuildDate>Sat, 20 Apr 2013 20:15:34 +0000</lastBuildDate>
    <atom:link href="https://bjornjohansen.com/tag/varnish/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Restricting access to WordPress login by IP address</title>
      <link>https://bjornjohansen.com/restricting-access-to-wordpress-login-by-ip-address/</link>
      <pubDate>Sat, 20 Apr 2013 20:15:34 +0000</pubDate>
       <guid isPermaLink="false">urn:uuid:33306539-3032-5330-b562-623835343236</guid> 
      <description>If you have a static IP address, like from &lt;a href=&#34;https://www.bjornjohansen.com/setting-up-your-own-pptp-vpn&#34;&gt;your own VPN&lt;/a&gt;, it is very easy to increase your security tremendously. Simply restrict all logins to that IP address.</description>
    </item>
    <item>
      <title>Caching: Varnish or Nginx?</title>
      <link>https://bjornjohansen.com/caching-varnish-or-nginx/</link>
      <pubDate>Fri, 12 Apr 2013 20:37:57 +0000</pubDate>
       <guid isPermaLink="false">urn:uuid:63636330-6461-5163-b365-333638366266</guid> 
      <description>TL;DR: Varnish lacks support for SSL and SPDY. Nginx handles it just fine, and has very fast cache with either memcache or disk storage (ramdisk). Both can serve stale cache if your backend is down. But Nginx can not write to the memcache storage directly, it has to be done by the application. Also, Nginx can not purge the cache itself, without you compiling your own package.</description>
    </item>
  </channel>
</rss>
