<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Tidio on CSP Guide</title>
    <link>https://csp-guide.com/tags/tidio/</link>
    <description>Recent content in Tidio on CSP Guide</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 09 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://csp-guide.com/tags/tidio/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CSP for Tidio Live Chat: A Practical Setup Guide</title>
      <link>https://csp-guide.com/posts/csp-for-tidio-live-chat/</link>
      <pubDate>Sun, 09 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>https://csp-guide.com/posts/csp-for-tidio-live-chat/</guid>
      
      <description>&lt;p&gt;Tidio is one of those integrations that looks trivial until your CSP blocks half of it.&lt;/p&gt;
&lt;p&gt;You paste the widget snippet, refresh, and the chat bubble never appears. Then DevTools starts yelling about &lt;code&gt;script-src&lt;/code&gt;, &lt;code&gt;connect-src&lt;/code&gt;, &lt;code&gt;frame-src&lt;/code&gt;, maybe &lt;code&gt;img-src&lt;/code&gt;, and sometimes even &lt;code&gt;style-src&lt;/code&gt;. If your site already has a reasonably locked-down policy, Tidio will force you to be explicit.&lt;/p&gt;
&lt;p&gt;I’ve had better results treating chat widgets like mini-applications instead of “just another script”. They load scripts, open WebSocket connections, render frames, fetch images, and inject styles. Your CSP has to allow that behavior without turning into &lt;code&gt;default-src * &#39;unsafe-inline&#39; &#39;unsafe-eval&#39;&lt;/code&gt;.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
