<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ssl on Marco&#39;s Blog</title>
    <link>https://www.mrgazz.com/tags/ssl/</link>
    <description>Recent content in Ssl on Marco&#39;s Blog</description>
    <generator>Hugo</generator>
    <language>en</language>
    <managingEditor>marco@mrgazz.com (Marco)</managingEditor>
    <webMaster>marco@mrgazz.com (Marco)</webMaster>
    <lastBuildDate>Fri, 21 Oct 2016 15:45:02 +0000</lastBuildDate>
    <atom:link href="https://www.mrgazz.com/tags/ssl/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>SSL Certificates with Let&#39;s Encrypt</title>
      <link>https://www.mrgazz.com/post/2016-10-21-ssl-certificates-letsencrypt/</link>
      <pubDate>Fri, 21 Oct 2016 15:45:02 +0000</pubDate><author>marco@mrgazz.com (Marco)</author>
      <guid>https://www.mrgazz.com/post/2016-10-21-ssl-certificates-letsencrypt/</guid>
      <description>&lt;p&gt;You probably noticed a microscopic difference when accessing the site: suddenly, when you type in mrgazz.com, you get redirected to the secure site, &amp;lt;&amp;gt;. Why, and how?&lt;/p&gt;&#xA;&lt;p&gt;First the why: Google announced it was going to prioritize search results according to the security of the site. That makes a lot of sense: “secure” sites have a modicum of respectability and require extra work compared to plain HTTP sites. You have to set up a secure server, which means you have to do more than simply point a DNS name to an IP address.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
