<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Vimeo on CSP Guide</title>
    <link>https://csp-guide.com/tags/vimeo/</link>
    <description>Recent content in Vimeo on CSP Guide</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 18 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://csp-guide.com/tags/vimeo/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CSP for Vimeo Embeds: What to Allow and What to Avoid</title>
      <link>https://csp-guide.com/posts/csp-for-vimeo-embeds/</link>
      <pubDate>Sat, 18 Jul 2026 00:00:00 +0000</pubDate>
      
      <guid>https://csp-guide.com/posts/csp-for-vimeo-embeds/</guid>
      
      <description>&lt;p&gt;Embedding Vimeo looks simple until your Content Security Policy blocks it.&lt;/p&gt;
&lt;p&gt;I’ve seen this happen a lot: the iframe is added, everything works locally, then production ships with a stricter CSP and the player turns into a blank rectangle. The fix usually isn’t “allow everything from &lt;code&gt;https:&lt;/code&gt;” unless you enjoy undoing the point of CSP.&lt;/p&gt;
&lt;p&gt;For Vimeo embeds, the main question is how strict you want to be while still letting the player work. There are a few workable patterns, and each has tradeoffs.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
