<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Cache on sigtar.com</title>
		<link>https://sigtar.com/tags/cache/</link>
		<description>Recent content in Cache on sigtar.com</description>
		<generator>Hugo</generator>
		<language>en-nz</language>
		
		
		
		
			<lastBuildDate>Mon, 15 Oct 2018 00:00:00 +1300</lastBuildDate>
		
			<atom:link href="https://sigtar.com/tags/cache/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>SSL caching and redirects in chrome</title>
				<link>https://sigtar.com/2018/10/15/nginx-ssl-caching-and-redirects-in-chrome/</link>
				<pubDate>Mon, 15 Oct 2018 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2018/10/15/nginx-ssl-caching-and-redirects-in-chrome/</guid>
				<description>&lt;p&gt;&lt;a href=&#34;https://sigtar.com/2018/10/15/nginx-ssl-caching-in-chrome/capture-6/&#34;&gt;&lt;img src=&#34;https://sigtar.com/wp-content/uploads/Capture-4.png&#34; alt=&#34;&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;While setting up SSL reverse proxy using lets encrypt and nginx i  had a few troubles with testing via googles Chrome browser.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Chrome caches some SSL responses which can be cleared by deleting your browsing data via settings or Ctrl+Shift+Del.&lt;/li&gt;&#xA;&lt;li&gt;Chrome also caches http -&amp;gt; https redirects, you can see these by going to chrome://net-internals and select “HSTS” from the drop down. Enter the domain name under “Delete domain” and press the Delete button&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;The easiest thing to do during &lt;strong&gt;testing&lt;/strong&gt; is use &lt;strong&gt;incognito mode&lt;/strong&gt;. You will not need to clear the cache every time you change config or re-issue certificates.&lt;/p&gt;</description>
			</item>
			<item>
				<title>bye bye http - hello letsencrypt</title>
				<link>https://sigtar.com/2018/10/11/bye-bye-http-hello-letsencrypt/</link>
				<pubDate>Thu, 11 Oct 2018 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2018/10/11/bye-bye-http-hello-letsencrypt/</guid>
				<description>&lt;p&gt;&lt;a href=&#34;https://sigtar.com/2018/10/11/bye-bye-http-hello-letsencrypt/capture-5/&#34;&gt;&lt;img src=&#34;https://sigtar.com/wp-content/uploads/Capture-3.png&#34; alt=&#34;&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve been a fan of HTTP and caching since my dial-up modem.&lt;/p&gt;&#xA;&lt;p&gt;Skip to today where google returns HTTPS sites higher in its search results. Its could also be possible that you cannot trust a man in the middle HTTP cache any longer either right? :)&lt;/p&gt;&#xA;&lt;p&gt;SSL certs have traditionally been expensive, but say welcome to lets encrypt which provides a free way of securing all of your websites. If you haven&amp;rsquo;t heard of it check it out here - &lt;a href=&#34;https://letsencrypt.org/&#34;&gt;https://letsencrypt.org/&lt;/a&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>zfs : accidentally adding cache drive to raidz zpool</title>
				<link>https://sigtar.com/2011/05/04/zfs-accidentally-adding-cache-drive-to-raidz-zpool/</link>
				<pubDate>Wed, 04 May 2011 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2011/05/04/zfs-accidentally-adding-cache-drive-to-raidz-zpool/</guid>
				<description>&lt;p&gt;&lt;a href=&#34;http://forums.freebsd.org/showthread.php?t=23127&#34;&gt;http://forums.freebsd.org/showthread.php?t=23127&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;Unfortunately if you have accidentally added a single drive into your raidz pool at the top-level there is no way to just remove the non redundant disk. Your pool is now &lt;strong&gt;dependant&lt;/strong&gt; on this disk.&lt;/p&gt;&#xA;&lt;p&gt;If you want your pool to be just raidz vdevs, then you will need to backup your data, destroy your pool, create a new pool, and restore your data.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;There is no current way to remove a top-level vdev from a pool.&lt;/strong&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>Squid - optimizing cache hits</title>
				<link>https://sigtar.com/2009/06/10/squid-optimizing-cache-hits/</link>
				<pubDate>Wed, 10 Jun 2009 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2009/06/10/squid-optimizing-cache-hits/</guid>
				<description>&lt;p&gt;The first place to look for increasing your hit ratio is the &lt;em&gt;refresh_pattern&lt;/em&gt; parameter within the &lt;strong&gt;squid.conf&lt;/strong&gt; file.&lt;/p&gt;&#xA;&lt;p&gt;Note: the following applies to squid 3.0 and higher only&amp;hellip;.&lt;/p&gt;&#xA;&lt;p&gt;I have found a really good page here &lt;a href=&#34;http://linux.com/archive/feature/153221&#34;&gt;http://linux.com/archive/feature/153221&lt;/a&gt; that explains some good setups if you with to increase your cache hits&amp;hellip;&lt;/p&gt;&#xA;&lt;p&gt;&lt;em&gt;refresh_pattern ^ftp: 1440 20% 10080 refresh_pattern ^gopher: 1440 0% 1440 refresh_pattern -i \.(gif|png|jpg|jpeg|ico)$ 10080 90% 43200 override-expire ignore-no-cache ignore-no-store ignore-private refresh_pattern -i \.(iso|avi|wav|mp3|mp4|mpeg|swf|flv|x-flv)$ 43200 90% 432000 override-expire ignore-no-cache ignore-no-store ignore-private refresh_pattern -i \.(deb|rpm|exe|zip|tar|tgz|ram|rar|bin|ppt|doc|tiff)$ 10080 90% 43200 override-expire ignore-no-cache ignore-no-store ignore-private refresh_pattern -i \.index.(html|htm)$ 0 40% 10080 refresh_pattern -i \.(html|htm|css|js)$ 1440 40% 40320 refresh_pattern . 0 40% 40320&lt;/em&gt;&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
