<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Soundcloud on CSP Guide</title>
    <link>https://csp-guide.com/tags/soundcloud/</link>
    <description>Recent content in Soundcloud on CSP Guide</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 22 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://csp-guide.com/tags/soundcloud/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CSP for SoundCloud Embeds: A Real-World Before/After</title>
      <link>https://csp-guide.com/posts/csp-for-soundcloud-embeds/</link>
      <pubDate>Wed, 22 Jul 2026 00:00:00 +0000</pubDate>
      
      <guid>https://csp-guide.com/posts/csp-for-soundcloud-embeds/</guid>
      
      <description>&lt;p&gt;If you’ve ever dropped a SoundCloud player into a page and thought “it’s just an iframe, what could go wrong?”, CSP will answer that pretty quickly.&lt;/p&gt;
&lt;p&gt;I’ve seen this exact failure pattern on otherwise well-locked-down sites: strong baseline policy, analytics and consent tooling carefully whitelisted, &lt;code&gt;object-src &#39;none&#39;&lt;/code&gt;, &lt;code&gt;frame-ancestors &#39;none&#39;&lt;/code&gt;, all the good stuff. Then somebody adds a SoundCloud embed and the player just shows a blank box or refuses to load.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
