<p>The httpd's core modules offer a predefinined list of hooks
used during the standard <a href="./request.html">request processing</a>
phase. Creating a new hook will expose a function that
- implements it (see sections below) but it is essential to undestand that you will not
+ implements it (see sections below) but it is essential to understand that you will not
extend the httpd's core hooks. Their presence and order in the request processing is in fact
a consequence of how they are called in <code>server/request.c</code>
(check <a href="./modguide.html#hooking">this section</a>
<p>Reading <a href="./modguide.html">guide for developing modules</a> and
<a href="./request.html">request processing</a> before proceeding is
- highly recomended.
+ highly recommended.
</p>
</section>
<p>All other headers are ignored. Cookies will also not be copied over. PUSHing resources
that require a cookie to be present will not work. This can be a matter of debate. But
unless this is more clearly discussed with browser, let's err on the side of caution and
- not expose cookie where they might oridinarily not be visible.</p>
+ not expose cookie where they might ordinarily not be visible.</p>
</section>
<section id="earlyhints">
The <directive module="mod_proxy">ProxyPass</directive>
directive specifies the mapping of incoming requests to the backend
server (or a cluster of servers known as a <code>Balancer</code>
- group). The simpliest example proxies all requests (<code>"/"</code>)
+ group). The simplest example proxies all requests (<code>"/"</code>)
to a single backend:
</p>
The inverse process of switching from Basic to Digest
Authentication without assigning new passwords is generally
not possible. Only if the Basic Authentication passwords
- have been stored in plain text or with a reversable encryption
+ have been stored in plain text or with a reversible encryption
scheme will it be possible to recover them and generate a
new data store following the Digest Authentication password
storage scheme.
should list the locations that will be protected by this
configuration.</p>
- <p>The pasword file referenced in the <directive
+ <p>The password file referenced in the <directive
module="mod_auth_digest">AuthUserFile</directive> directive may be
created and managed using the <program>htdigest</program> tool.</p>
<seealso><a href="../misc/password_encryptions.html">Password Formats</a></seealso>
<section id="socache">
-<title>Performance and Cacheing</title>
+<title>Performance and Caching</title>
<p>Some users of DBD authentication in HTTPD 2.2/2.4 have reported that it
imposes a problematic load on the database. This is most likely where
an HTML page contains hundreds of objects (e.g. images, scripts, etc)
the Authentication and DBD frameworks.</p>
<highlight language="config">
# mod_dbd configuration
-# UPDATED to include authentication cacheing
+# UPDATED to include authentication caching
DBDriver pgsql
DBDParams "dbname=apacheauth user=apache password=xxxxxx"
<status>Base</status>
<sourcefile>mod_authz_host.c</sourcefile>
<identifier>authz_host_module</identifier>
-<compatibility>The <code>forward-dns</code> provider was addded in 2.4.19</compatibility>
+<compatibility>The <code>forward-dns</code> provider was added in 2.4.19</compatibility>
<summary>
<p>The authorization providers implemented by <module>mod_authz_host</module> are
as usual. If you also specify a <directive
module="mod_autoindex">ReadmeName</directive>, and if that file
exists, The closing </body></html> tags are also
- ommitted from the output, under the assumption that you'll likely
+ omitted from the output, under the assumption that you'll likely
put those closing tags in that file.</dd>
<dt><a name="indexoptions.suppressicon"
filter runs <em>any</em> provider.</p>
<p>Flags specified with this directive are merged with the flags
- that underlying providers may have registerd with
+ that underlying providers may have registered with
<module>mod_filter</module>. For example, a filter may internally specify
the equivalent of <code>change=yes</code>, but a particular
configuration of the module can override with <code>change=no</code>.
all bandwidth allocated to Y can be used by X.
</p>
<p>
- When a stream has more than one dependant, say X1 and X2 both
+ When a stream has more than one dependent, say X1 and X2 both
depend on Y, the <em>weight</em> determines the bandwidth
allocation. If X1 and X2 have the same weight, they both get
half of the available bandwidth. If the weight of X1 is twice
<p>
When configuring numbits of 1-8, a random number in range
[0, 2^numbits[ are added to each frame. The random value is chosen
- independantly for each frame that the module sends back to the client.
+ independently for each frame that the module sends back to the client.
</p>
<p>
While more padding bytes give better message length obfuscation, they
to the usual set of CGI variables.</p>
<p>The use of <code><a href="#includevirtual"
- >#include virtual</a></code> is almost always prefered to using
+ >#include virtual</a></code> is almost always preferred to using
either <code>#exec cgi</code> or <code>#exec cmd</code>. The former
(<code>#include virtual</code>) uses the standard Apache sub-request
mechanism to include files or scripts. It is much better tested and
<dt>"default"</dt>
<dd> <p> When set to "default", the underlying SDK's referral chasing state
is not changed, <directive>LDAPReferralHopLimit</directive> is not
- used to overide the SDK's hop limit, and no LDAP rebind callback is
+ used to override the SDK's hop limit, and no LDAP rebind callback is
registered.</p></dd>
</dl>
function filter(r)
-- Our first yield is to signal that we are ready to receive buckets.
-- Before this yield, we can set up our environment, check for conditions,
- -- and, if we deem it necessary, decline filtering a request alltogether:
+ -- and, if we deem it necessary, decline filtering a request altogether:
if something_bad then
return -- This would skip this filter.
end
</p>
<p>
You can override this default in either way. If you specify 'always',
- the module will renew certificates for an MD, irregardless if the
+ the module will renew certificates for an MD, regardless if the
domains are in use or if there are static files.
</p>
<p>
<p>
Sets challenge types (in order of preference) when proving domain ownership.
Supported by the module are the challenge methods 'tls-alpn-01', 'dns-01'
- and 'http-01'. The module will look at the overall configuation of the server
+ and 'http-01'. The module will look at the overall configuration of the server
to find out which methods can be used.
</p><p>
If the server listens on port 80, for example, the 'http-01' method is available.
<p>
mod_md offers an implementation for providing OCSP stapling information.
This is an alternative to the one provided by 'mod_ssl'. For backward
- compatiblity, this is disabled by default.
+ compatibility, this is disabled by default.
</p><p>
The stapling can be switched on for all certificates on the server or
for an individual MDomain. This will replace any stapling configuration
If the validity of the OCSP response used in stapling falls below 'duration',
mod_md will obtain a new OCSP response.
</p><p>
- The CA issueing a certificate commonly also operates the OCSP responder
+ The CA issuing a certificate commonly also operates the OCSP responder
service and determines how long its signed response about the validity
of a certificate are itself valid. The longer a response is valid, the longer
it can be cached which mean better overall performance for everyone.
a path info appended to the URL using a semicolon (<code>;</code>)
as the separator and add the session id behind. As in the cookie case,
Apache Tomcat can include the configured <code>jvmRoute</code> in this path
- info. To let Apache find this sort of path info, you neet to set
+ info. To let Apache find this sort of path info, you need to set
<code>scolonpathdelim</code> to <code>On</code> in
<directive module="mod_proxy">ProxyPass</directive> or
<directive module="mod_proxy">ProxySet</directive>.</p>
or regex of a subsequent one.</dd>
</dl>
- <p>The <var>substitution</var> is may contain literal text and regular
+ <p>The <var>substitution</var> may contain literal text and regular
expression backreferences</p>
<example><title>Example</title>
</example>
<p>The character which is used to separate (or "delimit") the
- various parts of the substituion string is referred to as the
+ various parts of the substitution string is referred to as the
"delimiter", and it is most common to use a slash for this
purpose.</p>
<p>This also means that multiple instances of Apache httpd configured on a
same <code>IP:port</code> and with a positive <directive>ListenCoresBucketsRatio</directive>
would start without an error too, and then run with incoming connections
- evenly distributed accross both instances (this is NOT a recommendation or
+ evenly distributed across both instances (this is NOT a recommendation or
a sensible usage in any case, but just a notice that it would prevent such
possible issues to be detected).</p>
<p>Within the same instance, Apache httpd will check and fail to start if
<p>The Server consists of a main, parent process and a small, static
number of child processes.</p>
- <p>The parent process' job is to manage the child processes. This
+ <p>The parent process's job is to manage the child processes. This
involves spawning children as required to ensure there are always
<directive module="mpm_common">StartServers</directive> processes
accepting connections.</p>
<example>
Netware\build netware-libc nw-nasm enable-mdc2 enable-md5
</example>
- Warning: dont use the CodeWarrior Assembler - it produces broken code!
+ Warning: don't use the CodeWarrior Assembler - it produces broken code!
</li>
<li>Before building Apache, set the environment variable
</highlight>
</li>
- <li>This solution uses the captured value in the URL subsitution,
+ <li>This solution uses the captured value in the URL substitution,
discarding the rest of the original query by appending a '?':
<highlight language="config">
</highlight>
<p>The <a id="mapfunc" name="mapfunc"><em>MapName</em></a> is an
- arbitray name that you assign to the map, and which you will use in
+ arbitrary name that you assign to the map, and which you will use in
directives later on. Arguments are passed to the map via the
following syntax:</p>
<!ATTLIST glossary ref CDATA #IMPLIED>
<!-- The phonetic element should be used only within the glossary. It
- describes a pronounciation -->
+ describes a pronunciation -->
<!ELEMENT phonetic (#PCDATA)>
</xsl:template>
-<!-- Value-of used here explicitly because we don't wan't latex-escaping
+<!-- Value-of used here explicitly because we don't want latex-escaping
performed. Of course, this will conflict with html where some tags are
interpreted in pre -->
<xsl:template match="pre|highlight">
<!-- ==================================================================== -->
<!-- <context> -->
-<!-- Each entry is separeted with a comma -->
+<!-- Each entry is separated with a comma -->
<!-- ==================================================================== -->
<xsl:template match="context">
<xsl:choose>
* recognized.
*
* Shortcut is an optional string of characters, any of which, if the first
- * character, gurantee that this pattern and only this pattern matches.
+ * character, guarantee that this pattern and only this pattern matches.
*
* @param {Array} shortcutStylePatterns patterns that always start with
* a known character. Must have a shortcut string.
<xsl:call-template name="pre" />
</pre>&lf; <!-- /.highlight -->
</xsl:template>
-<!-- /higlight -->
+<!-- /highlight -->
<!-- ==================================================================== -->
<!-- ==================================================================== -->
<!-- Filter   in text() nodes. -->
<!-- In some environments this character won't be transformed correctly, -->
-<!-- so we just write it explicitely as " " into the output. -->
+<!-- so we just write it explicitly as " " into the output. -->
<!-- ==================================================================== -->
<xsl:template match="text()" name="filter.nbsp">
<xsl:param name="text" select="." />
<xsl:text># in order to be ready to use for the JS used in prettify.js</xsl:text>&lf;
&lf;
<xsl:text># The next line has to be copy/pasted into prettify.js around line 135</xsl:text>&lf;
-<xsl:text># in place of the correponding CONFIG_KEYWORDS array.</xsl:text>&lf;
+<xsl:text># in place of the corresponding CONFIG_KEYWORDS array.</xsl:text>&lf;
&lf;
<xsl:variable name="directives"
&lf;
&lf;
<xsl:text># The next line has to be copy/pasted into prettify.js around line 920</xsl:text>&lf;
-<xsl:text># in place of the correponding PR_TAG array.</xsl:text>&lf;
+<xsl:text># in place of the corresponding PR_TAG array.</xsl:text>&lf;
&lf;
<xsl:text> [PR_TAG, /^\b(</xsl:text>
* dealings in this Software without prior written authorization
* from the individuals in question.
*
- * Any stylesheet derived from this Software that is publically
+ * Any stylesheet derived from this Software that is publicly
* distributed will be identified with a different name and the
* version strings in any derived Software will be changed so that
* no possibility of confusion between the derived package and this
</xsl:choose>
</xsl:variable>
- <!-- The line below is not splitted in multiple
+ <!-- The line below is not split into multiple
lines to avoid rendering a broken URL. -->
<a href="https://bz.apache.org/bugzilla/buglist.cgi?bug_status=__open__&list_id=144532&product=Apache%20httpd-2&query_format=specific&order=changeddate%20DESC%2Cpriority%2Cbug_severity&component={$bugzilla_prefix}{name}">
</a>
</li>
<li>
- <!-- The line below is not splitted in multiple
+ <!-- The line below is not split into multiple
lines to avoid rendering a broken URL. -->
<a href="https://bz.apache.org/bugzilla/enter_bug.cgi?product=Apache%20httpd-2&component={$bugzilla_prefix}{name}">
<xsl:value-of
<!-- ==================================================================== -->
<!-- <context> -->
-<!-- Each entry is separeted with a comma -->
+<!-- Each entry is separated with a comma -->
<!-- ==================================================================== -->
<xsl:template match="context">
<xsl:choose>
to ensure safe operations?</strong>
<p class="indent">
- suEXEC cleans the process' environment by establishing a
+ suEXEC cleans the process's environment by establishing a
safe execution PATH (defined during configuration), as
well as only passing through those variables whose names
are listed in the safe environment list (also created
projects / thirdparty / apache / httpd.git / commitdiff
