'REDIRECT_' onto the original header name. This provides the error
document the context of the original request.</p>
- <p>For example, you might recieve, in addition to more usual
+ <p>For example, you might receive, in addition to more usual
environment variables, the following.</p>
<example>
<p>If you point your <code>ErrorDocument</code> to some variety of
dynamic handler such as a server-side include document, CGI
script, or some variety of other handler, you may wish to use the
- available custom environent variables to customize this
+ available custom environment variables to customize this
response.</p>
<p>If the ErrorDocument specifies a local redirect to a CGI
major releases (for example, from 2.0 to 2.2 or from 2.2 to 2.3),
there will likely be major differences in the compile-time and
run-time configuration that will require manual adjustments. All
- modules will also need to be upgraded to accomodate changes in the
+ modules will also need to be upgraded to accommodate changes in the
module API.</p>
<p>Upgrading from one minor version to the next (for example, from
circumvent this issue.</p>
<p>Note that if you have a wildcard SSL certificate, or a
- certificate that has multple hostnames on it using subjectAltName
+ certificate that has multiple hostnames on it using subjectAltName
fields, you can use SSL on name-based virtual hosts without further
workarounds.</p>
</section>
<p>OpenSSL 0.9.8 started to support this by default when compiled with the
<code>zlib</code> option. If both the client and the server support compression,
it will be used. However, most clients still try to initially connect with an
-SSLv2 Hello. As SSLv2 did not include an array of prefered compression algorithms
+SSLv2 Hello. As SSLv2 did not include an array of preferred compression algorithms
in its handshake, compression cannot be negotiated with these clients.
If the client disables support for SSLv2, either an SSLv3 or TLS Hello
may be sent, depending on which SSL library is used, and compression may
<section id="configexample">
<title>Basic Configuration Example</title>
-<p>Your SSL configuration will need to contain, at a minumum, the
+<p>Your SSL configuration will need to contain, at minimum, the
following directives.</p>
<example>
to start a session. To do this, the server assigns each SSL session a
unique session identifier which is cached in the server and which the
client can use in future connections to reduce the handshake time
- (until the session identifer expires from the cache of the server).</p>
+ (until the session identifier expires from the cache of the server).</p>
</note>
<p class="figure">
<p class="indent">
If it doesn't exist, it can't very well contain files. If we
- can't change directory to it, it might aswell not exist.
+ can't change directory to it, it might as well not exist.
</p>
</li>