Skip to content

Magento 2.3.5 Csp Issue #30804

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

Closed
abhishekc3 opened this issue Nov 5, 2020 · 5 comments
Closed

Magento 2.3.5 Csp Issue #30804

abhishekc3 opened this issue Nov 5, 2020 · 5 comments

Comments

@abhishekc3
Copy link

abhishekc3 commented Nov 5, 2020

Preconditions (*)

  1. Magento CE/EE 2.3.5 without Sample Data (composer installation)
  2. Nginx 1.10.3 (PHP 7.3.21).
  3. Default Nginx config used (nginx.conf.sample).

Steps to reproduce (*)

  1. Navigate to URL: Click a form in home page.

Expected result (*)

  1. Form Url should open.

Actual result (*)

  1. Error - 502 Bad Gateway.

image

Summary of the issue:
I have created a custom CSP module for removing the browser console warnings. In module, I created two files config.xml and csp_whitelist.xml. When I enable this module i get the above error but when I disable the module my website is running properly.

config.xml
image

csp_whitelist.xml
image

@m2-assistant
Copy link

m2-assistant bot commented Nov 5, 2020

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

Please, add a comment to assign the issue: @magento I am working on this


⚠️ 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, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

@hostep
Copy link
Contributor

hostep commented Nov 5, 2020

Could maybe be related to #29964 (which has a fix in 047629a) but it's hard to say without more info. Maybe you can find more info the Magento and/or webserver log files?

@iphigenie
Copy link

Could maybe be related to #29964 (which has a fix in 047629a)

the symptom would be 1) cache taking a lot more space than it used to and 2) out of memory errors in the logs

@tim-breitenstein-it
Copy link

Could maybe be related to #29964 (which has a fix in 047629a) but it's hard to say without more info. Maybe you can find more info the Magento and/or webserver log files?

Is it possible to fix this temporary with an custom module?

@stale
Copy link

stale bot commented Feb 4, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!

@stale stale bot added the stale issue label Feb 4, 2021
@stale stale bot closed this as completed Feb 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants