<?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>Netlify on Sirius Stuff</title>
    <link>https://www.siriusventures.com/tags/netlify/</link>
    <description>Recent content in Netlify on Sirius Stuff</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 28 Oct 2020 01:01:01 -0700</lastBuildDate>
    <atom:link href="https://www.siriusventures.com/tags/netlify/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Moving from AWS S3 and Cloudfront to Netlify</title>
      <link>https://www.siriusventures.com/moving-from-aws-s3-and-cloudfront-to-netlify/</link>
      <pubDate>Wed, 28 Oct 2020 01:01:01 -0700</pubDate>
      <guid>https://www.siriusventures.com/moving-from-aws-s3-and-cloudfront-to-netlify/</guid>
      <description>&lt;p&gt;After almost 10 years of letting the blog sit, I wanted to bring it into the modern world.   One of the issues was that I had last touched the blog back in 2011 when SSL connections were only for transactions.   The blog was just fine serving pages at https:// but the rest of the world has moved onto https://   Notice the &amp;ldquo;s&amp;rdquo; for HyperText TransPort Secure.&lt;/p&gt;
&lt;p&gt;I was able to do that with some work but the biggest problem was that most of my URLs end in / but some didn&amp;rsquo;t.  I was able to find a blog post on how to use Lamdas from AWS called from Cloudfront to handle adding a &amp;ldquo;/&amp;rdquo; to requests.   But some-url/ and some-url and some-url/index.html were treated differently.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
