Commit 06abb0d9 authored by Martin Kraemer's avatar Martin Kraemer
Browse files

It's -> its (where appropriate) 


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@91874 13f79535-47bb-0310-9956-ffa450edef68
parent 0faf05ba

docs/manual/ssl/ssl_faq.html

+3 −3
Original line number Diff line number Diff line
@@ -292,7 +292,7 @@ What about mod_ssl and the Wassenaar Arrangement? 
</strong>&nbsp;&nbsp;

    [<a href="http://httpd.apache.org/docs-2.0/ssl/ssl_faq.html#wassenaar"><b>L</b></a>]

    <p>

    First, let us explain what <i>Wassenaar</i> and it's <i>Arrangement on

    First, let us explain what <i>Wassenaar</i> and its <i>Arrangement on

    Export Controls for Conventional Arms and Dual-Use Goods and

    Technologies</i> is: This is a international regime, established 1995, to

    control trade in conventional arms and dual-use goods and technology. It
@@ -504,7 +504,7 @@ How can I speak HTTPS manually for testing purposes? 
    <code><b>$ telnet localhost 80</b></code><br>

    <code><b>GET / HTTP/1.0</b></code>

    <p>

    for simple testing the HTTP protocol of Apache, it's not such easy for

    for simple testing the HTTP protocol of Apache, it's not so easy for

    HTTPS because of the SSL protocol between TCP and HTTP. But with the

    help of OpenSSL's <code>s_client</code> command you can do a similar

    check even for HTTPS:

docs/manual/ssl/ssl_faq.wml

+2 −2
Original line number Diff line number Diff line
@@ -231,7 +231,7 @@ Is mod_ssl Year 2000 compliant? 
What about mod_ssl and the Wassenaar Arrangement?

</faq>



    First, let us explain what <i>Wassenaar</i> and it's <i>Arrangement on

    First, let us explain what <i>Wassenaar</i> and its <i>Arrangement on

    Export Controls for Conventional Arms and Dual-Use Goods and

    Technologies</i> is: This is a international regime, established 1995, to

    control trade in conventional arms and dual-use goods and technology. It
@@ -424,7 +424,7 @@ How can I speak HTTPS manually for testing purposes? 
    <code><b>$ telnet localhost 80</b></code><br>

    <code><b>GET / HTTP/1.0</b></code>

    <p>

    for simple testing the HTTP protocol of Apache, it's not such easy for

    for simple testing the HTTP protocol of Apache, it's not so easy for

    HTTPS because of the SSL protocol between TCP and HTTP. But with the

    help of OpenSSL's <code>s_client</code> command you can do a similar

    check even for HTTPS:

docs/manual/ssl/ssl_howto.html

+3 −3
Original line number Diff line number Diff line
@@ -45,7 +45,7 @@ is not always obvious because of the coherences between SSL, HTTP and Apache's 
way of processing requests. This chapter gives instructions on how to solve

such typical situations. Treat is as a first step to find out the final

solution, but always try to understand the stuff before you use it. Nothing is

worse than using a security solution without knowing it's restrictions and

worse than using a security solution without knowing its restrictions and

coherences.



<ul>
@@ -174,7 +174,7 @@ find in the <code>README.GlobalID</code> document in the mod_ssl distribution. 
In short: The server has a Global ID server certificate, signed by a special

CA certificate from Verisign which enables strong encryption in export

browsers. This works as following: The browser connects with an export cipher,

the server sends it's Global ID certificate, the browser verifies it and

the server sends its Global ID certificate, the browser verifies it and

subsequently upgrades the cipher suite before any HTTP communication takes

place. The question now is: How can we allow this upgrade, but enforce strong

encryption. Or in other words: Browser either have to initially connect with

docs/manual/ssl/ssl_howto.wml

+2 −2
Original line number Diff line number Diff line
@@ -21,7 +21,7 @@ is not always obvious because of the coherences between SSL, HTTP and Apache's 
way of processing requests. This chapter gives instructions on how to solve

such typical situations. Treat is as a first step to find out the final

solution, but always try to understand the stuff before you use it. Nothing is

worse than using a security solution without knowing it's restrictions and

worse than using a security solution without knowing its restrictions and

coherences.



</td>
@@ -121,7 +121,7 @@ find in the <code>README.GlobalID</code> document in the mod_ssl distribution. 
In short: The server has a Global ID server certificate, signed by a special

CA certificate from Verisign which enables strong encryption in export

browsers. This works as following: The browser connects with an export cipher,

the server sends it's Global ID certificate, the browser verifies it and

the server sends its Global ID certificate, the browser verifies it and

subsequently upgrades the cipher suite before any HTTP communication takes

place. The question now is: How can we allow this upgrade, but enforce strong

encryption. Or in other words: Browser either have to initially connect with

docs/manual/ssl/ssl_reference.html

+3 −3
Original line number Diff line number Diff line
@@ -600,7 +600,7 @@ in the global server context because the PRNG is a global facility. 
The following <em>source</em> variants are available:

<ul>

<li><code>builtin</code>

    <p> This is the always available builtin seeding source. It's usage

    <p> This is the always available builtin seeding source. Its usage

    consumes minimum CPU cycles under runtime and hence can be always used

    without drawbacks. The source used for seeding the PRNG contains of the

    current time, the current process id and (when applicable) a randomly
@@ -638,7 +638,7 @@ The following <em>source</em> variants are available: 
    find under <i>rndcontrol(8)</i> on those platforms. Alternatively, when

    your system lacks such a random device, you can use tool

    like <a href="http://www.lothar.com/tech/crypto/">EGD</a>

    (Entropy Gathering Daemon) and run it's client program with the

    (Entropy Gathering Daemon) and run its client program with the

    <code>exec:/path/to/program/</code> variant (see below) or use

    <code>egd:/path/to/egd-socket</code> (see below).

<p>
@@ -974,7 +974,7 @@ The available (case-insensitive) <em>protocol</em>s are: 
    This is the Transport Layer Security (TLS) protocol, version 1.0. It is the

    successor to SSLv3 and currently (as of February 1999) still under

    construction by the Internet Engineering Task Force (IETF). It's still

    not supported by any popular browsers.

    not supported by all popular browsers.

<p>

<li><code>All</code>

    <p>