Hi I’d like to do some testing of Discourse without necessarily going through its configured public domain name. For eg if Discourse have been installed and configured as https://uat.mysite.com then I can obviously load my browser and browse to https://uat.mysite.com , which means my browser would …

[Bild] titusc: which means my browser would exit my internal network out to public Internet to resolve the domain name to it’s public IP address, and load the pages via its public IP address. Then configure your machine to resolve that address to the local ip of the discourse server. There ar…

I actually tried /etc/hosts but still having the same error due to CSP. I’d have thought that there is a flag or setting that can be used to toggle this to enable the developers to do everything within their laptop without having to stand up a DNS solution. Looking at the Install Discourse on macO…

[Bild] titusc: is there a way to either disable CSP There is a site setting named content security policy. You can uncheck and save to disable CSP. As long as this is not done in production instance it’s okay.

[Bild] titusc: The challenge I have is I have automation to install Discourse and want to use the same process to stand up both development, UAT, and production environments That’s not a good idea. It will never work. A development environment is necessity different as it has assets precompil…

[Bild] titusc: I’d like to do some testing of Discourse without necessarily going through its configured public domain name. Hi! I regularly do this, but with Docker installs. Assuming that you use our standard Docker installation in production, then for your acceptance testing you should be …

Wie man die Content Security Policy entspannt

Entwickler

Falco (Falco) 11. November 2022 um 05:34 4

Es gibt eine Website-Einstellung namens content security policy. Sie können das Kontrollkästchen deaktivieren und speichern, um CSP zu deaktivieren.

Solange dies nicht in einer Produktionsinstanz geschieht, ist es in Ordnung.

Thema		Antworten	Aufrufe
Content Security Policy: The settings of the page have blocked the loading of a resource ("script-src") Self-hosting unsupported-install	27	2495	3. Mai 2023
Fresh Discourse install on digitalocean, cannot activate account Self-hosting	14	1689	21. Januar 2019
Port forwarding? Support	2	917	30. Januar 2020
Mitigate XSS Attacks with Content Security Policy Site Management how-to , content-security-policy	30	25689	13. Juni 2023
Local installation internal use only Self-hosting	11	1246	9. März 2024

Wie man die Content Security Policy entspannt

Verwandte Themen