# 外部 nginx pagespeed モジュールがセキュリティポリシー違反を引き起こす

**URL:** <https://meta.discourse.org/t/external-nginx-pagespeed-module-causes-security-policy-violation/121336>\
**Category:** Self-hosting\
**Created:** [2019 年 6 月 25 日午後 11:59 UTC](https://meta.discourse.org/t/external-nginx-pagespeed-module-causes-security-policy-violation/121336 "2019-06-25T23:59:38Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\
**Post date:** [2019 年 6 月 27 日午後 3:24 UTC](https://meta.discourse.org/t/external-nginx-pagespeed-module-causes-security-policy-violation/121336/12 "2019-06-27T15:24:30Z")

</div>

> [@34563463456](#):
>
> 私は通常、デフォルトで `pagespeed on;` にしています。

それは現代では悪い考えです:

> [@Install ngx\_pagespeed](https://meta.discourse.org/t/install-ngx-pagespeed/110218/2?u=falco):
>
> It will create only problems. The ngx\_pagespeed was made when you can’t change the underlying website and need to fix it at the reverse proxy layer. Discourse already implements all the needed bits, compression, cache headers, etc.

---

_[View the full topic](https://meta.discourse.org/t/external-nginx-pagespeed-module-causes-security-policy-violation/121336)._