See: <a href="ssl/">SSL/TLS Encryption</a>
</dd>
- <dt><a name="regularexpresion" id="regularexpresion">Regular Expression</a>
+ <dt><a name="regularexpression" id="regularexpression">Regular Expression</a>
<a name="regex" id="regex">(Regex)</a></dt>
<dd>A way of describing a pattern in text - for example, "all the words that
begin with the letter A" or "every 10-digit phone number" or even "Every
<p>matches directories in <code>/www/</code> (or any subdirectory thereof)
that consist of three numbers.</p>
- <note><title>Compatability</title>
+ <note><title>Compatibility</title>
Prior to 2.3.9, this directive implicitly applied to sub-directories
(like <directive module="core" type="section">Directory</directive>) and
could not match the end of line symbol ($). In 2.3.9 and later,
<directivesynopsis>
<name>AuthLDAPBindPassword</name>
-<description>Password used in conjuction with the bind DN</description>
+<description>Password used in conjunction with the bind DN</description>
<syntax>AuthLDAPBindPassword <em>password</em></syntax>
<contextlist><context>directory</context><context>.htaccess</context>
</contextlist>
<usage>
<p>The <directive>CacheMaxExpire</directive> directive specifies the maximum number of
- seconds for which cachable HTTP documents will be retained without checking the origin
+ seconds for which cacheable HTTP documents will be retained without checking the origin
server. Thus, documents will be out of date at most this number of seconds. This maximum
value is enforced even if an expiry date was supplied with the document.</p>
<usage>
<p>The <directive>CacheMinExpire</directive> directive specifies the minimum number of
- seconds for which cachable HTTP documents will be retained without checking the origin
+ seconds for which cacheable HTTP documents will be retained without checking the origin
server. This is only used if no valid expire time was supplied with the document.</p>
<li><code>/someapplication/image.gif;jsessionid=123456789</code></li>
<li><code>/someapplication/image.gif?PHPSESSIONID=12345678</code></li>
</ul>
- <p>This causes cachable resources to be stored separately for each session, which
+ <p>This causes cacheable resources to be stored separately for each session, which
is often not desired. <directive>CacheIgnoreURLSessionIdentifiers</directive> lets
define a list of identifiers that are removed from the key that is used to identify
- an entity in the cache, such that cachable resources are not stored separately for
+ an entity in the cache, such that cacheable resources are not stored separately for
each session.
</p>
<p><code>CacheIgnoreURLSessionIdentifiers None</code> clears the list of ignored
<p>Both CA and client certificates may be specified globally
(LDAPTrustedGlobalCert) or per-connection (LDAPTrustedClientCert).
When any settings are specified per-connection, the global
- settings are superceded.</p>
+ settings are superseded.</p>
<p>The documentation for the SDK claims to support both SSL and
STARTTLS, however STARTTLS does not seem to work on all versions
</highlight>
<highlight language="lua">
-r:mkdir(dir [,mode]) -- Creates a directory and sets mode to optional mode paramter.
+r:mkdir(dir [,mode]) -- Creates a directory and sets mode to optional mode parameter.
</highlight>
<highlight language="lua">
-r:mkrdir(dir [,mode]) -- Creates directories recursive and sets mode to optional mode paramter.
+r:mkrdir(dir [,mode]) -- Creates directories recursive and sets mode to optional mode parameter.
</highlight>
<highlight language="lua">
<tr>
<td>qslast|QSL</td>
<td>Interpret the last (right-most) question mark as the query string
- delimeter, instead of the first (left-most) as normally used.
+ delimiter, instead of the first (left-most) as normally used.
Available in 2.4.19 and later.
<em><a href="../rewrite/flags.html#flag_qsl">details
...</a></em></td>
will use the new <directive module="mod_ssl">SSLProxyCheckPeerName</directive>
behavior, and all configurations which disable either one of the
<code>SSLProxyCheckPeerName</code> or <code>SSLProxyCheckPeerCN</code> options
-will supress all remote server certificate name validation. Only the following
+will suppress all remote server certificate name validation. Only the following
configuration will trigger the legacy certificate CN comparison in 2.4.21 and
later releases;
</p>
<dt>const char *create(ap_socache_instance_t **instance, const char *arg,
apr_pool_t *tmp, apr_pool_t *p);</dt>
<dd>Create a session cache based on the given configuration string.
- The instance pointer returned in the instance paramater will be
+ The instance pointer returned in the instance parameter will be
passed as the first argument to subsequent invocations.</dd>
<dt>apr_status_t init(ap_socache_instance_t *instance, const char *cname,
>AC96</a>, ch13].</p>
</section>
-<section id="digestfuntion">
+<section id="digestfunction">
<title>Digest Function</title>
<p>The choice of digest function determines how a digest is created
from a record unit. SSL supports the following:</p>
projects / apache / commitdiff