Allow to load base64 encoded images and fonts

[vovayatsyuk]

Description

Current Content Security Policy setup doesn't allow to load images and fonts via data: scheme which is quite a popular method to load local resources (base64 encoded images). Additionally, it's used internally by the browser cache (Chrome) when you refresh the page.

Manual testing scenarios (*)

1. Open Luma homepage and open browser console.
2. Refresh the page to trigger resource loading from the browser cache.
3. Inspect errors in the console:

4. Apply the patch, and try again. No errors should appear in the log.

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• All automated tests passed successfully (all builds are green)

Resolved issues:

1. resolves [Issue] Allow to load base64 encoded images and fonts #31170: Allow to load base64 encoded images and fonts

[m2-assistant]

Hi @vovayatsyuk. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento give me test instance - deploy test instance based on PR changes
• @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE,
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests

You can find more information about the builds here

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

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

⚠️ According to the Magento Contribution requirements, all Pull Requests 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 Pull Requests 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

[sidolov]

@magento create issue

[gabrieldagama]

@magento run all tests

[gabrieldagama]

@magento run all tests

[aleron75]

Hi @vovayatsyuk thanks for your contribution.

Can you please take a look at the failing \Magento\Csp\Model\Collector\ConfigCollectorTest and fix it?

Thank you

[vovayatsyuk]

Done.

[engcom-Foxtrot]

@magento run all tests

[engcom-Charlie]

@magento run all tests

[engcom-Charlie]

@magento run Integration Tests

[magento-engcom-team]

Hi @sidolov, thank you for the review.
ENGCOM-8577 has been created to process this Pull Request

[engcom-Alfa]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @engcom-Alfa. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @engcom-Alfa, here is your Magento Instance: https://354a2f4d539797723e2d5eade8412513-2-4-develop.instances.magento-community.engineering
Admin access: https://354a2f4d539797723e2d5eade8412513-2-4-develop.instances.magento-community.engineering/admin_326e
Login: 7b58c74d
Password: 6499a303d248

[engcom-Alfa]

✔️ QA Passed

Manual testing scenario:

1. Add Base64 encoded image to home page;
2. Open Luma homepage and open browser console.
3. Refresh the page to trigger resource loading from the browser cache.
4. Inspect errors in the console:

Before: ✖️ Refuse to load the image...

After: ✔️ Image and font uploaded successfully without any errors

[m2-assistant]

Hi @vovayatsyuk, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.