Skip to content
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

Open
5 tasks
Naberdz opened this issue Feb 13, 2025 · 6 comments
Open
5 tasks

Content policy #39626

Naberdz opened this issue Feb 13, 2025 · 6 comments
Assignees
Labels
Issue: needs update Additional information is require, waiting for response Reported on 2.4.7-p3 Indicates original Magento version for the Issue report.

Comments

@Naberdz
Copy link

Naberdz commented Feb 13, 2025

Preconditions and environment

  • Magento version 2.4.7-p3
  • Magento version 2.4.6-p8

Steps to reproduce

  1. Set a store with domain name without www
  2. Generate static content
  3. Visit site it will work as normal.
  4. Visit site with www prepended to a domain name

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

  • Severity: S0 - Affects critical data or functionality and leaves users without workaround.
  • Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
  • Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
  • Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
  • Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.
Copy link

m2-assistant bot commented Feb 13, 2025

Hi @Naberdz. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.


Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

@engcom-Bravo engcom-Bravo added the Reported on 2.4.7-p3 Indicates original Magento version for the Issue report. label Feb 13, 2025
@github-project-automation github-project-automation bot moved this to Ready for Confirmation in Issue Confirmation and Triage Board Feb 13, 2025
@engcom-Delta engcom-Delta self-assigned this Feb 13, 2025
Copy link

m2-assistant bot commented Feb 13, 2025

Hi @engcom-Delta. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

  • 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
  • 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
  • 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
  • 4. Verify that the issue is reproducible on 2.4-develop branch
    Details- If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
  • 5. Add label Issue: Confirmed once verification is complete.
  • 6. Make sure that automatic system confirms that report has been added to the backlog.

@engcom-Delta
Copy link
Contributor

Hi @Naberdz ,

Thanks for your reporting and collaboration.
We have tried to reproduce the issue in Latest 2.4-develop instance and we are not able to reproduce the issue. Kindly refer the screenshot.

Steps to reproduce

  1. Set a store with domain name without www

Image

  1. Generate static content
  2. Visit site it will work as normal.

Image

  1. User need to provide www if we want the url to work with www.
    e.g.

Image
5. Access frontend url with www

Image

Thanks.

@engcom-Delta engcom-Delta added the Issue: needs update Additional information is require, waiting for response label Feb 13, 2025
@Naberdz
Copy link
Author

Naberdz commented Feb 13, 2025

@engcom-Delta

you don't need to chnage your domain in settings to have www.

so base url in magento2 settings is example.com
if you access site with www.example.com

you will get errors with content policy.

@engcom-Bravo engcom-Bravo moved this from Ready for Confirmation to Needs Update in Issue Confirmation and Triage Board Feb 13, 2025
@hostep
Copy link
Contributor

hostep commented Feb 13, 2025

@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.

@Naberdz
Copy link
Author

Naberdz commented Feb 14, 2025

@hostep
wel for any other non magento site you can visit it with or without www and once you click on any link you will be sent to correct base url.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: needs update Additional information is require, waiting for response Reported on 2.4.7-p3 Indicates original Magento version for the Issue report.
Projects
Development

No branches or pull requests

4 participants