<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Sentry on CSP Guide</title>
    <link>https://csp-guide.com/tags/sentry/</link>
    <description>Recent content in Sentry on CSP Guide</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 27 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://csp-guide.com/tags/sentry/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CSP for Sentry: Copy-Paste Policies and Debugging</title>
      <link>https://csp-guide.com/posts/csp-for-sentry-error-tracking/</link>
      <pubDate>Thu, 27 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>https://csp-guide.com/posts/csp-for-sentry-error-tracking/</guid>
      
      <description>&lt;p&gt;Sentry is usually the first thing that breaks when you tighten a Content Security Policy.&lt;/p&gt;
&lt;p&gt;That makes sense. Sentry’s browser SDK wants to send network requests, sometimes open tunnels through your own domain, sometimes upload source maps in CI, and occasionally capture session replay data. A strict CSP blocks all of that unless you explicitly allow it.&lt;/p&gt;
&lt;p&gt;If you just want the answer: for Sentry in the browser, &lt;code&gt;connect-src&lt;/code&gt; is the directive that matters most.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
