From ed8334e91b07b5f6c43a59a2e3c58c6a1de2171a Mon Sep 17 00:00:00 2001 From: Daniel Gruno Date: Mon, 29 Apr 2013 12:19:14 +0000 Subject: [PATCH] Expand on how to set context specific directives. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1476984 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/developer/modguide.xml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/docs/manual/developer/modguide.xml b/docs/manual/developer/modguide.xml index 01e8e1f80a..3acb280306 100644 --- a/docs/manual/developer/modguide.xml +++ b/docs/manual/developer/modguide.xml @@ -1184,8 +1184,19 @@ AP_INIT_TAKE1("exampleEnabled", example_set_enabled, NULL, RSRC_CONF, "Enable or this directive in a global server context, but since we are now trying out a context aware version of our module, we should set this to something more lenient, namely the value ACCESS_CONF, which lets us use -the directive inside <Directory> and <Location> blocks. +the directive inside <Directory> and <Location> blocks. For more +control over the placement of your directives, you can combine the following +restrictions together to form a specific rule:

+
Using the server to allocate configuration slots -- 2.50.1