on Unix and Unix-like systems only. For compiling and
installation on Windows, see <a
href="platform/windows.html">Using Apache HTTP Server with Microsoft
- Windows</a> and <a
+ Windows</a> and <a
href="platform/win_compiling.html">Compiling Apache for Microsoft Windows</a>.
For other platforms, see the <a
href="platform/">platform</a> documentation.</p>
projects.</p>
<p>If you are upgrading from one minor version to the next (for
- example, 2.4.
9 to 2.4.10), please skip down to the <a
+ example, 2.4.
8 to 2.4.9), please skip down to the <a
href="#upgrading">upgrading</a> section.</p>
</summary>
(be sure the directory names do not have version numbers; for example,
the APR distribution must be under /httpd_source_tree_root/srclib/apr/) and use
<code>./configure</code>'s <code>--with-included-apr</code>
- option. On some platforms, you may have to install the
- corresponding <code>-dev</code> packages to allow httpd to build
+ option. On some platforms, you may have to install the
+ corresponding <code>-dev</code> packages to allow httpd to build
against your installed copy of APR and APR-Util.</dd>
<dt>Perl-Compatible Regular Expressions Library (PCRE)</dt>
- <dd>This library is required but not longer bundled with httpd.
- Download the source code from <a href="http://www.pcre.org/">http://www.pcre.org</a>,
+ <dd>This library is required but not longer bundled with httpd.
+ Download the source code from <a href="http://www.pcre.org/">http://www.pcre.org</a>,
or install a Port or Package. If your build system can't find
the pcre-config script installed by the PCRE build, point to it
- using the <code>--with-pcre</code> parameter. On some platforms,
- you may have to install the corresponding <code>-dev</code>
- package to allow httpd to build against your installed copy
+ using the <code>--with-pcre</code> parameter. On some platforms,
+ you may have to install the corresponding <code>-dev</code>
+ package to allow httpd to build against your installed copy
of PCRE.</dd>
-
+
<dt>Disk Space</dt>
<dd>Make sure you have at least 50 MB of temporary free disk
space available. After installation the server occupies
<p>A <a
href="http://wiki.apache.org/httpd/DistrosDefaultLayout">description
- of these third-party distrubutions</a> is maintained in the HTTP
+ of these third-party distributions</a> is maintained in the HTTP
Server wiki, and should reflect the current state of these
third-party distributions. However, you will need to familiarize
yourself with your particular platform's package management and
<highlight language="config">
<DirectoryMatch "^/var/www/combined/(?<SITENAME>[^/]+)">
- require ldap-group "cn=%{env:MATCH_SITENAME},ou=combined,o=Example"
+ Require ldap-group "cn=%{env:MATCH_SITENAME},ou=combined,o=Example"
</DirectoryMatch>
</highlight>
<li><directive>Directory</directive> "/" matches and an initial configuration to set the <code>CustomHeaderName</code> header with the value <code>one</code> is created.</li>
<li><directive>Directory</directive> "/example" matches, and since <module>mod_headers</module> specifies in its code to override in case of a merge, a new configuration is created to set the <code>CustomHeaderName</code> header with the value <code>two</code>.</li>
<li><directive>FilesMatch</directive> ".*" matches and another merge opportunity arises, causing the <code>CustomHeaderName</code> header to be set with the value <code>three</code>.</li>
- <li>Eventually during the next steps of the HTTP request processing <module>mod_headers</module> will be called and it will receive the configuration to set the <code>CustomHeaderName</code> header with the value <code>three</code>. <module>mod_headers</module> normally uses this configuration to perfom its job, namely setting the foo header. This does not mean that a module can't perform a more complex action like discarding directives because not needed or deprecated, etc..</li>
+ <li>Eventually during the next steps of the HTTP request processing <module>mod_headers</module> will be called and it will receive the configuration to set the <code>CustomHeaderName</code> header with the value <code>three</code>. <module>mod_headers</module> normally uses this configuration to perform its job, namely setting the foo header. This does not mean that a module can't perform a more complex action like discarding directives because not needed or deprecated, etc..</li>
</ul>
<p>This is true for .htaccess too since they have the same priority as <directive>Directory</directive> in the merge order. The important concept to understand is that configuration sections like <directive>Directory</directive> and <directive>FilesMatch</directive> are not comparable to module specific directives like <directive module="mod_headers">Header</directive> or <directive module="mod_rewrite">RewriteRule</directive> because they operate on different levels.
Warnings & Examples</title>
<p><strong>NOTE!</strong> This section may not be
- complete. For the latest revision of this section of the
- documentation, see the <a
- href="http://httpd.apache.org/docs/&httpd.docs;/suexec.html">Online
- Documentation</a> version.</p>
+ complete.</p>
<p>There are a few points of interest regarding
the wrapper that can cause limitations on server setup. Please
review these before submitting any "bugs" regarding suEXEC.</p>
+ <p><strong>suEXEC Points Of Interest</strong></p>
<ul>
- <li><strong>suEXEC Points Of Interest</strong></li>
<li>
Hierarchy limitations
projects / thirdparty / apache / httpd.git / commitdiff
