# Nginx as reverse proxy and Content Security Policy issue

**URL:** <https://meta.discourse.org/t/nginx-as-reverse-proxy-and-content-security-policy-issue/322288>\
**Category:** Self-hosting\
**Tags:** nginx\
**Created:** [August 19, 2024, 3:55pm UTC](https://meta.discourse.org/t/nginx-as-reverse-proxy-and-content-security-policy-issue/322288 "2024-08-19T15:55:18Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\
**Post date:** [August 19, 2024, 5:09pm UTC](https://meta.discourse.org/t/nginx-as-reverse-proxy-and-content-security-policy-issue/322288/6 "2024-08-19T17:09:02Z")

</div>

> [@sandra.mccollum](#):
>
> If I comment out the policy, it all works as expected…

That’s good. Commenting out the NGINX config means that the CSP header set by Discourse should be passed through 🎉

---

_[View the full topic](https://meta.discourse.org/t/nginx-as-reverse-proxy-and-content-security-policy-issue/322288)._