<?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>immutable on {bjørn:johansen}</title>
    <link>https://bjornjohansen.com/tag/immutable/</link>
    <description>Recent content in immutable on {bjørn:johansen}</description>
    <generator>Hugo -- 0.118.2</generator>
    <language>en-US</language>
    <lastBuildDate>Tue, 21 Mar 2017 19:47:48 +0000</lastBuildDate>
    <atom:link href="https://bjornjohansen.com/tag/immutable/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Immutable assets with unique URLs in WordPress for enqueued JS and CSS files</title>
      <link>https://bjornjohansen.com/immutable-assets-wordpress/</link>
      <pubDate>Tue, 21 Mar 2017 19:47:48 +0000</pubDate>
       <guid isPermaLink="false">urn:uuid:36313862-3266-5261-b061-663763373839</guid> 
      <description>If you’re utilizing the browser cache correctly, you’ll gain huge performance benefits for your users, as well as save bandwidth and server capacity which equals to saving money. To do this right, you must create unique URLs for all versions of your resources, and tell them to never ask for the content again by telling the browsers that the assets are immutable resources.</description>
    </item>
  </channel>
</rss>
