diff options
| author | Luca Toscano <elukey@apache.org> | 2017-08-18 10:24:45 +0200 |
|---|---|---|
| committer | Luca Toscano <elukey@apache.org> | 2017-08-18 10:24:45 +0200 |
| commit | 05ed8fd266bbe2d005ab22f52b198245fb2b7295 (patch) | |
| tree | f5a6c65210fcdc88c219009a4537b987ee0018cd /docs/manual/developer | |
| parent | doc xsl/dtd: introduce idtype attribute for directivesynopsis (diff) | |
| download | apache2-05ed8fd266bbe2d005ab22f52b198245fb2b7295.tar.xz apache2-05ed8fd266bbe2d005ab22f52b198245fb2b7295.zip | |
Documentation rebuild
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1805373 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'docs/manual/developer')
| -rw-r--r-- | docs/manual/developer/API.html.en | 6 | ||||
| -rw-r--r-- | docs/manual/developer/request.html.en | 8 |
2 files changed, 7 insertions, 7 deletions
diff --git a/docs/manual/developer/API.html.en b/docs/manual/developer/API.html.en index 9d15f7a7a5..8df5cb78ea 100644 --- a/docs/manual/developer/API.html.en +++ b/docs/manual/developer/API.html.en @@ -309,7 +309,7 @@ point to per-module configuration structures. Specifically, these hold pointers to the data structures which the module has built to describe the way it has been configured to operate in a given directory (via - <code>.htaccess</code> files or <code class="directive"><a href="../mod/core.html#directorysection"><Directory></a></code> sections), for private data it has built in the + <code>.htaccess</code> files or <code class="directive"><a href="../mod/core.html#directory"><Directory></a></code> sections), for private data it has built in the course of servicing the request (so modules' handlers for one phase can pass `notes' to their handlers for other phases). There is another such configuration vector in the <code>server_rec</code> data structure pointed @@ -911,7 +911,7 @@ void *request_config; /* Notes on *this* request */</pre><p><code> filesystem, following the translated pathname, to read any <code>.htaccess</code> files which might be present. The information which is read in then has to be <em>merged</em> with the applicable information - from the server's own config files (either from the <code class="directive"><a href="../mod/core.html#directorysection"><Directory></a></code> sections in + from the server's own config files (either from the <code class="directive"><a href="../mod/core.html#directory"><Directory></a></code> sections in <code>access.conf</code>, or from defaults in <code>srm.conf</code>, which actually behaves for most purposes almost exactly like <code><Directory /></code>).</p> @@ -937,7 +937,7 @@ void *request_config; /* Notes on *this* request */</pre><p><code> table *encoding_types; /* Added with AddEncoding... */ } mime_dir_config;</pre></div> - <p>When the server is reading a configuration file, or <code class="directive"><a href="../mod/core.html#directorysection"><Directory></a></code> section, which includes + <p>When the server is reading a configuration file, or <code class="directive"><a href="../mod/core.html#directory"><Directory></a></code> section, which includes one of the MIME module's commands, it needs to create a <code>mime_dir_config</code> structure, so those commands have something to act on. It does this by invoking the function it finds in the module's diff --git a/docs/manual/developer/request.html.en b/docs/manual/developer/request.html.en index 5f97d7f163..c0de1bd487 100644 --- a/docs/manual/developer/request.html.en +++ b/docs/manual/developer/request.html.en @@ -99,7 +99,7 @@ <h3><a name="inital-location-walk" id="inital-location-walk">Initial URI Location Walk</a></h3> <p>Every request is subject to an <code>ap_location_walk()</code> call. This ensures that - <code class="directive"><a href="../mod/core.html#locationsection"><Location></a></code> sections + <code class="directive"><a href="../mod/core.html#location"><Location></a></code> sections are consistently enforced for all requests. If the request is an internal redirect or a sub-request, it may borrow some or all of the processing from the previous or parent request's ap_location_walk, so this step @@ -122,11 +122,11 @@ <p>After the file or correct URI was determined, the appropriate per-dir configurations are merged together. For example, <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code> compares and merges the appropriate - <code class="directive"><a href="../mod/mod_proxy.html#proxysection"><Proxy></a></code> sections. + <code class="directive"><a href="../mod/mod_proxy.html#proxy"><Proxy></a></code> sections. If the URI is nothing more than a local (non-proxy) <code>TRACE</code> request, the core handles the request and returns <code>DONE</code>. If no module answers this hook with <code>OK</code> or <code>DONE</code>, - the core will run the request filename against the <code class="directive"><a href="../mod/core.html#directorysection"><Directory></a></code> and <code class="directive"><a href="../mod/core.html#filessection"><Files></a></code> sections. If the request + the core will run the request filename against the <code class="directive"><a href="../mod/core.html#directory"><Directory></a></code> and <code class="directive"><a href="../mod/core.html#files"><Files></a></code> sections. If the request 'filename' isn't an absolute, legal filename, a note is set for later termination.</p> @@ -135,7 +135,7 @@ <p>Every request is hardened by a second <code>ap_location_walk()</code> call. This reassures that a translated request is still subjected to the configured - <code class="directive"><a href="../mod/core.html#locationsection"><Location></a></code> sections. + <code class="directive"><a href="../mod/core.html#location"><Location></a></code> sections. The request again borrows some or all of the processing from its previous <code>location_walk</code> above, so this step is almost always very efficient unless the translated URI mapped to a substantially different |