httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1476991 - /httpd/httpd/branches/2.4.x/docs/manual/developer/modguide.xml
Date Mon, 29 Apr 2013 12:22:39 GMT
Author: humbedooh
Date: Mon Apr 29 12:22:38 2013
New Revision: 1476991

Expand on how to set context specific directives. Also fix some typos


Modified: httpd/httpd/branches/2.4.x/docs/manual/developer/modguide.xml
--- httpd/httpd/branches/2.4.x/docs/manual/developer/modguide.xml (original)
+++ httpd/httpd/branches/2.4.x/docs/manual/developer/modguide.xml Mon Apr 29 12:22:38 2013
@@ -304,7 +304,7 @@ looks like 
 <p>The most essential part of any request is the <em>request record
 </em>. In a call to a handler function, this is represented by the <code>
 request_rec* </code> structure passed along with every call that is made. 
-This struct, typically just refered to as <code>r</code> in modules, 
+This struct, typically just referred to as <code>r</code> in modules, 
 contains all the information you need for your module to fully process any 
 HTTP request and respond accordingly.</p> <p>Some key elements of the <code>
 request_rec </code> structure are:
@@ -709,7 +709,7 @@ static int example_handler(request_rec *
-This version in its entirity can be found here: 
+This version in its entirety can be found here: 
 <a href="">mod_example_2.c</a>.
@@ -892,7 +892,7 @@ set them.</em>)
 <section id="directive_handler"><title>The directive handler function</title>
-Now that we've told the server to expect some directives for our module, it's 
+Now that we have told the server to expect some directives for our module, it's 
 time to make a few functions for handling these. What the server reads in the 
 configuration file(s) is text, and so naturally, what it passes along to 
 our directive handler is one or more strings, that we ourselves need to 
@@ -1184,8 +1184,19 @@ AP_INIT_TAKE1("exampleEnabled", example_
 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 <code>ACCESS_CONF</code>, which lets us use 
-the directive inside &lt;Directory&gt; and &lt;Location&gt; blocks.
+the directive inside &lt;Directory&gt; and &lt;Location&gt; blocks. For more

+control over the placement of your directives, you can combine the following 
+restrictions together to form a specific rule:
+<li><code>RSRC_CONF</code>: Allow in .conf files (not .htaccess) outside
&lt;Directory&gt; or &lt;Location&gt;</li>
+<li><code>ACCESS_CONF</code>: Allow in .conf files (not .htaccess) inside
&lt;Directory&gt; or &lt;Location&gt;</li>
+<li><code>OR_OPTIONS</code>: Allow in .conf files and .htaccess when <code>AllowOverride
Options</code> is set</li>
+<li><code>OR_FILEINFO</code>: Allow in .conf files and .htaccess when <code>AllowOverride
FileInfo</code> is set</li>
+<li><code>OR_AUTHCFG</code>: Allow in .conf files and .htaccess when <code>AllowOverride
AuthConfig</code> is set</li>
+<li><code>OR_INDEXES</code>: Allow in .conf files and .htaccess when <code>AllowOverride
Indexes</code> is set</li>
+<li><code>OR_ALL</code>: Allow anywhere in .conf files and .htaccess</li>
 <section id="context_pool"><title>Using the server to allocate configuration
@@ -1619,7 +1630,7 @@ static int example_handler(request_rec *
     keyValuePair* formData;
-    formData = readPost();
+    formData = readPost(r);
     if (formData) {
         int i;
         for (i = 0; formData[i]; i++) {

View raw message