Csp module enhancement

[HirokazuNishi]

Description (*)

Csp module is bundled in Magento 2.3.5 and later, but it causes really noisy error messages when we enable browser's developer tool. This situation is caused by "no report-uri" value in CSP header.

Expected behavior (*)

Current default CSP header mode is "report only", but it should be used in developer mode. CSP header should be disabled in other modes by default. Also to add cli or admin configuration page for switching CSP header is nice.

Benefits

Current implementation is really noisy for production/deault environment. To improve CSP module, we can show CSP "report only mode" result for developers only.

Environment

• Magento 2.3.5
• Google Chrome 81.0.4044.129 on Mac OS 10.15.4

Steps to Reproduce

1. Install vanilla Magento 2.3.5 with sample data.
2. Enable developer tool on your browser.
3. Access to any page you want.
4. Check console and you can see CSP error message.

[m2-assistant]

Hi @HirokazuNishi. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

@HirokazuNishi do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant]

Hi @shikhamis11. 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).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - 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.

[nathanjosiah]

Hello @shikhamis11. This is expected behavior. We have plans of rolling out a reporting endpoint but this feature is not as simple as it would seem to be. For now, it is expected to have your own endpoint if you wish to use the feature. I would recommend https://report-uri.com/

[flancer64]

@HirokazuNishi , I've created module to collect CSP reports and generate rules to eliminate error spam in console - https://github.com/flancer32/mage2_ext_csp You can try to use it.