<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Openreplay on CSP Guide</title>
    <link>https://csp-guide.com/tags/openreplay/</link>
    <description>Recent content in Openreplay on CSP Guide</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 16 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://csp-guide.com/tags/openreplay/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>OpenReplay CSP Mistakes That Break Session Replay</title>
      <link>https://csp-guide.com/posts/csp-for-openreplay-session-replay/</link>
      <pubDate>Thu, 16 Jul 2026 00:00:00 +0000</pubDate>
      
      <guid>https://csp-guide.com/posts/csp-for-openreplay-session-replay/</guid>
      
      <description>&lt;p&gt;OpenReplay is one of those tools that looks simple until CSP gets involved. You add the replay snippet, refresh the page, and nothing happens. No sessions, no network activity, maybe a vague console error if you are lucky.&lt;/p&gt;
&lt;p&gt;I’ve seen teams burn hours on this because the OpenReplay install itself is fine. The problem is usually CSP drift: a policy that made sense before replay was added, but now blocks the exact things replay needs.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
