Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (nike.apache.org: domain of covener@gmail.com designates
 209.85.212.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <08BE65B36BBC1B4E907E2015603B0DF30C0A35@smucm55a>
References: <08BE65B36BBC1B4E907E2015603B0DF30C0A35@smucm55a>
Date: Fri, 20 Feb 2015 07:53:16 -0500
Message-ID: 
 <CALK=YjNf8BmooKbZe2iqLt3Czuu4yrJ660jDumwbN4oDWUpBsQ@mail.gmail.com>
From: Eric Covener <covener@gmail.com>
To: users@httpd.apache.org
Content-Type: text/plain; charset=UTF-8
Subject: Re: [users@httpd] Execution order of directives within Apache 2.4

On Fri, Feb 20, 2015 at 7:33 AM,  <Andre.Wendel@bmw.de> wrote:
> Are there general rules, like the overall order inside the httpd.conf, or
> the execution is based on the order the single corresponding modules are
> loaded?


Directives are not directly excuted, they supply configuration to many
different modules.

Those modules all run in different stages of Apache processing.  They
can ask early, late, or before or after other modules they know about.
Sometimes, the order is undefined and can change over time.

So there is really no general rule other than how configurations
should be merged other than the precedence of the various
configuration sections:

http://httpd.apache.org/docs/2.4/sections.html

For example, DirectoryIndex specified multiple times might implicitly
add to the list, but using Require implicitly starts over fresh.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org