Apologies if this is the wrong Aegir project to post to. I'm not sure where Apache related things go. :)

Some changes in Apache 2.4 to how it handles config files affect Aegir.
Include /some/dir is no longer a valid way of including "everything", as apache will take this literally and try to include the content of the file "/some/dir", which fails for directories. Include /some/dir/* solves this. Next problem is that an Include with a *, that yields no files, will be considered an error as well, which will be the case with Include /var/aegir/config/server_master/apache/post.d/* most of the time.
IncludeOptional /var/aegir/config/server_master/apache/post.d/* solves this.

Comments

Letharion’s picture

Letharion commented
Project: Hostmaster (Aegir) » Provision

I realized this belongs in provision instead when I created the patch.

I would normally attach the patch here, since that's both best pratice and allows for a convenient work flow together with drush make. However, with non-module patches, this becomes quite inconvenient instead, as my gentoo packages can't use drush make. There's a large risk I'll update my patches and forget to attach them here then, so I just refrain from posting them to d.o until either a maintainer asks for it, or I feel certain they are "stable".

Link to patch dir: https://github.com/letharion/Gentoo-overlay/tree/master/app-admin/provis...

anarcat’s picture

anarcat commented
Status: Active » Needs work

Please do provide a patch or a link to a single commit.

From what I can tell in the patches you mention above, they are not backward-compatible with Apache 2.3, which is a significant problem. We want to retain backward compatibility as Apache 2.3 is the default webserver on a lot of systems out there.

Letharion’s picture

Letharion commented

Yeah, I've been trying to find a general solution. I got stuck though on the core .htaccess file, so I ended up posting a core issue instead. #1599774: Drupal fails to boot with 503 error and .htaccess protections do not work on Apache 2.4 without mod_access_compat.

gnassar’s picture

gnassar commented

Just to note: the .htaccess patch currently listed in post 25 of the cited issue above (#1599774: Drupal fails to boot with 503 error and .htaccess protections do not work on Apache 2.4 without mod_access_compat) seems to be working fine on my Drupal 6 install.

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
commented
Version: 6.x-1.x-dev » 7.x-3.x-dev
Issue summary: View changes

New features need to be implemented in Aegir 3.x, then we can consider back-porting to Aegir 2.x. Aegir 1.x is essentially deprecated.

steven jones’s picture

steven jones commented

So Drupal core has this issue, and the proposed patch at the moment suggests adding a ifmodule for a module that was added in Apache 2.3:

#1599774: Drupal fails to boot with 503 error and .htaccess protections do not work on Apache 2.4 without mod_access_compat

steven jones’s picture

steven jones commented
Related issues: +#1599774: Drupal fails to boot with 503 error and .htaccess protections do not work on Apache 2.4 without mod_access_compat
anarcat’s picture

anarcat commented
Status: Needs work » Postponed (maintainer needs more info)

Can we get an actual patch here?

In my current tests here, things seem to work fine, even in 1.x with patches for #2155445: 403 Forbidden in Ubuntu Saucy... So I would be tempted to mark this as "can't reproduce"...

anarcat’s picture

anarcat commented
Parent issue: » #2155705: [meta] Support Apache 2.4 (Ubuntu Saucy, Debian Jessie)

Mark as this related to 2.4 / ubuntu saucy (#2155705: [meta] Support Apache 2.4 (Ubuntu Saucy, Debian Jessie)).