<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Http on sigtar.com</title>
		<link>https://sigtar.com/tags/http/</link>
		<description>Recent content in Http 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/http/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>Corporate Firewall - SSH and port 443 goodness</title>
				<link>https://sigtar.com/2009/02/08/corporate-firewall-ssh-and-port-443-goodness/</link>
				<pubDate>Sun, 08 Feb 2009 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2009/02/08/corporate-firewall-ssh-and-port-443-goodness/</guid>
				<description>&lt;p&gt;Things you&amp;rsquo;ll need; (basic instructions) SSH - either Linux or Open SSH for windows (set this up first and ensure its working!). I have only used Linux, so i do not know the details of setting up a Open SSH box on windows (good luck).&lt;/p&gt;&#xA;&lt;p&gt;Router with pinhole or port forwarding abilities. &amp;ndash; forward your external 443 port to internal 22 on your SSH box&lt;/p&gt;&#xA;&lt;p&gt;Putty.exe - use this to test your SSH connection locally (you should be able to connect on port 22 locally or 443 externally)&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
