Skip to content
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

Add support of apache2.4 commands in htaccess #10810

Closed
s3rj1k opened this issue Sep 7, 2017 · 5 comments
Closed

Add support of apache2.4 commands in htaccess #10810

s3rj1k opened this issue Sep 7, 2017 · 5 comments
Assignees
Labels
Fixed in 2.2.x The issue has been fixed in 2.2 release line Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release

Comments

@s3rj1k
Copy link

s3rj1k commented Sep 7, 2017

Currently .htaccess template uses apache2.2 syntax

for example:

order allow,deny
deny from all

this needs to be updates for apache2.4 syntax

one could use conditional case for apache2 version like this

<IfVersion < 2.4> 
#... for 2.2
</IfVersion>
<IfVersion >= 2.4>
#... for 2.4
</IfVersion>
@TomashKhamlai
Copy link
Contributor

TomashKhamlai commented Sep 11, 2017

@s3rj1k, thank you for your report.
Please use the issue reporting guidelines to report an issue. Include the steps required to reproduce, the actual result, and the expected result. See the Issue reporting guidelines for more information.

@magento-engcom-team magento-engcom-team added Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed Progress: needs update labels Sep 11, 2017
@magento-engcom-team magento-engcom-team self-assigned this Sep 11, 2017
@magento-engcom-team magento-engcom-team added Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed 2.1.x Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release and removed Progress: needs update labels Sep 29, 2017
@magento-engcom-team
Copy link
Contributor

@s3rj1k, thank you for your report.
We've created internal ticket(s) MAGETWO-80868 to track progress on the issue.

@jonashrem
Copy link
Contributor

I'm working on it #SQUASHTOBERFEST

okorshenko pushed a commit that referenced this issue Nov 10, 2017
…pache >= 2.4 #11459

 - Merge Pull Request #11459 from jonashrem/magento2:2.2-develop
 - Merged commits:
   1. 64943cd
   2. 00937b1
@okorshenko okorshenko added the Fixed in 2.2.x The issue has been fixed in 2.2 release line label Nov 10, 2017
@mikelevy300
Copy link

Are there any plans to backport this to 2.1.x? The system requirements for Magento 2.1.x, http://devdocs.magento.com/guides/v2.1/install-gde/system-requirements-tech.html, say Apache 2.4 is supported, but without this fix, it won't work with 2.4. Seems like either this should be backported to 2.1.x or the documentation should be updated to say Magento 2.1.x only supports Apache 2.2.

@jonashrem
Copy link
Contributor

You can install mod_access_compat to use magento 2.1 with apache 2.4. Most installations come with it enabled.

https://httpd.apache.org/docs/2.4/mod/mod_access_compat.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Fixed in 2.2.x The issue has been fixed in 2.2 release line Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release
Projects
None yet
Development

No branches or pull requests

6 participants