<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Widgets on CSP Guide</title>
    <link>https://csp-guide.com/tags/widgets/</link>
    <description>Recent content in Widgets on CSP Guide</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 08 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://csp-guide.com/tags/widgets/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CSP for Calendly Booking Widget</title>
      <link>https://csp-guide.com/posts/csp-for-calendly-booking-widget/</link>
      <pubDate>Wed, 08 Jul 2026 00:00:00 +0000</pubDate>
      
      <guid>https://csp-guide.com/posts/csp-for-calendly-booking-widget/</guid>
      
      <description>&lt;p&gt;Calendly is one of those embeds that looks simple until CSP gets involved. You paste their widget script, add a button or inline container, and suddenly the browser starts screaming about blocked frames, styles, and network requests.&lt;/p&gt;
&lt;p&gt;I’ve had to wire this up a few times, and the tricky part is not “make it work.” The tricky part is making it work &lt;strong&gt;without&lt;/strong&gt; blowing a giant hole in your policy with &lt;code&gt;default-src *&lt;/code&gt; or a lazy &lt;code&gt;script-src &#39;unsafe-inline&#39; https:&lt;/code&gt;.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
