-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Content policy #39626
Comments
Hi @Naberdz. Thank you for your report.
Join Magento Community Engineering Slack and ask your questions in #github channel. |
Hi @engcom-Delta. Thank you for working on this issue.
|
Hi @Naberdz , Thanks for your reporting and collaboration. Steps to reproduce
Thanks. |
you don't need to chnage your domain in settings to have www. so base url in magento2 settings is example.com you will get errors with content policy. |
@Naberdz: that's how the system is designed, it will generate url's on the frontend based on the domain name in the configuration settings. Magento won't take just any domain name people happen to type into their browser thats points to your hosting and use it in the frontend. If you don't want people to end up on your shop using www, then generate a redirect rule in your webserver configuration to redirect them from www to non-www. Or alternatively, you could change the following config setting in Magento: Stores > Configuration > General > Web > Url Options > Auto-redirect to Base URL and set it to Yes. |
@hostep |
Preconditions and environment
Steps to reproduce
Expected result
Site should be working regardless of the www subdomain
Actual result
css/javascripts/images will not be loaded because it violates the content security policy
Additional information
No response
Release note
No response
Triage and priority
The text was updated successfully, but these errors were encountered: