<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Google on sigtar.com</title>
		<link>https://sigtar.com/tags/google/</link>
		<description>Recent content in Google 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/google/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>
	</channel>
</rss>
