<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Apache-Superset on CSP Guide</title>
    <link>https://csp-guide.com/tags/apache-superset/</link>
    <description>Recent content in Apache-Superset on CSP Guide</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 29 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://csp-guide.com/tags/apache-superset/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CSP Mistakes That Break Apache Superset Embeds</title>
      <link>https://csp-guide.com/posts/csp-for-apache-superset-embeds/</link>
      <pubDate>Sat, 29 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>https://csp-guide.com/posts/csp-for-apache-superset-embeds/</guid>
      
      <description>&lt;p&gt;Embedding Apache Superset sounds simple: generate an iframe, allow the host app, ship it. Then CSP shows up and quietly wrecks the whole thing.&lt;/p&gt;
&lt;p&gt;I’ve seen teams lose hours on this because the browser error messages are half-useful and Superset embeds have a few moving parts: iframe loading, API calls, auth endpoints, static assets, and whatever sits in front of Superset like Nginx, Apache, or a cloud proxy. One wrong directive and the embed either goes blank or fails in weird ways after login.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
