Skip to content

fix: remove end-of-life PHP version references from htaccess files#40684

Open
lbajsarowicz wants to merge 1 commit intomagento:2.4-developfrom
lbajsarowicz:fix/htaccess-remove-eol-php
Open

fix: remove end-of-life PHP version references from htaccess files#40684
lbajsarowicz wants to merge 1 commit intomagento:2.4-developfrom
lbajsarowicz:fix/htaccess-remove-eol-php

Conversation

@lbajsarowicz
Copy link
Copy Markdown
Contributor

Description

Remove references to end-of-life PHP versions (PHP 5.x and PHP 7.x) from .htaccess files.

Problem

Several .htaccess files contain:

  1. <IfModule mod_php7.c> blocks — Duplicate configuration blocks for PHP 7.x alongside the mod_php.c blocks for PHP 8+. PHP 7.4 (the last 7.x release) reached EOL in November 2022, and Magento 2.4.7+ requires PHP 8.2+.

  2. Suhosin extension referencephp_flag suhosin.session.cryptua off inside the mod_php7.c block. The Suhosin extension is abandoned and never supported PHP 7+, making this directive dead code even on PHP 7.

  3. PHP 5 CGI references — Commented-out php5-cgi handler, x-mapp-php5 type definitions, and php5.ini references from hosting-specific workarounds that are over a decade old.

Solution

  • Remove all <IfModule mod_php7.c> blocks (3 files)
  • Remove commented-out PHP 5 CGI handler section
  • Remove 1and1 hosting PHP 5 workaround
  • Remove GoDaddy CGI section referencing php5.ini
  • Keep all <IfModule mod_php.c> blocks (PHP 8+ compatible)

Files Changed

  • pub/.htaccess (remove mod_php7 block, suhosin, PHP 5 CGI/hosting sections)
  • pub/media/.htaccess (remove mod_php7 block)
  • pub/static/.htaccess (remove mod_php7 block)

⭐ 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
Copy link
Copy Markdown

m2-assistant bot commented Apr 10, 2026

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.

@lbajsarowicz
Copy link
Copy Markdown
Contributor Author

@magento run all tests

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant