fix: remove IE/Flash references and fix font MIME types in htaccess

[lbajsarowicz]

Description

Remove references to dead technologies (Internet Explorer, Adobe Flash) and update deprecated font MIME types to IANA-registered standards in .htaccess files.

Changes

1. Remove IE X-UA-Compatible header and document modes section

pub/.htaccess sets X-UA-Compatible: IE=edge and includes a large FilesMatch block to unset it on non-HTML resources. Internet Explorer is completely end-of-life:

• IE 11 reached EOL in June 2022
• Edge has used Chromium since January 2020
• No modern browser recognizes X-UA-Compatible

This removes the header, the FilesMatch exclusion block, and the explanatory comment section (~20 lines).

2. Remove Flash moxieplayer reference

pub/static/.htaccess contains a rewrite rule for moxieplayer.swf (a Flash-based media player). Adobe Flash reached end-of-life in December 2020 and is blocked by all modern browsers.

3. Fix deprecated font MIME types

Both pub/media/.htaccess and pub/static/.htaccess use non-standard application/x-font-* MIME types for fonts. These are replaced with the IANA-registered types:

Old (deprecated)	New (IANA standard)
application/x-font-ttf	font/ttf
application/x-font-otf	font/otf
application/x-font-woff	font/woff
application/font-woff2	font/woff2

Updated in both AddType directives and ExpiresByType directives.

Files Changed

• pub/.htaccess (IE section removal)
• pub/static/.htaccess (Flash removal + font MIME types)
• pub/media/.htaccess (font MIME types)

⭐ Support my work

Do you like the fix? Remember to react with "👍🏻" to get it merged faster,
Then Sponsor me on Github so I can spend more time on fixing issues like this one.

Learn more at https://github.com/sponsors/lbajsarowicz

[m2-assistant]

Hi @lbajsarowicz. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.
❗ 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
13. Semantic Version Checker

You can find more information about the builds here
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.

---

For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.