The referenced Makefile no longer exists, since mod_ssl is no longer a

separate distribution. If someone would like to provide more detail
here, that would be great. This is in response to
https://issues.apache.org/bugzilla/show_bug.cgi?id=49562


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

2 files changed, 12 insertions, 28 deletions

diff --git a/docs/manual/mod/mod_ssl.html.en b/docs/manual/mod/mod_ssl.html.en
index 50b8ce33fc..1b63ab730f 100644
--- a/docs/manual/mod/mod_ssl.html.en
+++ b/docs/manual/mod/mod_ssl.html.en
@@ -347,8 +347,7 @@ The files in this directory have to be PEM-encoded and are accessed through
 hash filenames. So usually you can't just place the Certificate files
 there: you also have to create symbolic links named
 <em>hash-value</em><code>.N</code>. And you should always make sure this directory
-contains the appropriate symbolic links. Use the <code>Makefile</code> which
-comes with mod_ssl to accomplish this task.</p>
+contains the appropriate symbolic links.</p>
 <div class="example"><h3>Example</h3><p><code>
 SSLCACertificatePath /usr/local/apache2/conf/ssl.crt/
 </code></p></div>
@@ -413,9 +412,7 @@ details.</p>
 through hash filenames. So usually you can't just place the
 Certificate files there: you also have to create symbolic links named
 <em>hash-value</em><code>.N</code>. And you should always make sure
-this directory contains the appropriate symbolic links. Use the
-<code>Makefile</code> which comes with mod_ssl to accomplish this
-task.</p>
+this directory contains the appropriate symbolic links.</p>
 <div class="example"><h3>Example</h3><p><code>
 SSLCADNRequestPath /usr/local/apache2/conf/ca-names.crt/
 </code></p></div>
@@ -499,8 +496,7 @@ The files in this directory have to be PEM-encoded and are accessed through
 hash filenames. So usually you have not only to place the CRL files there.
 Additionally you have to create symbolic links named
 <em>hash-value</em><code>.rN</code>. And you should always make sure this directory
-contains the appropriate symbolic links. Use the <code>Makefile</code> which
-comes with <code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code> to accomplish this task.</p>
+contains the appropriate symbolic links.</p>
 <div class="example"><h3>Example</h3><p><code>
 SSLCARevocationPath /usr/local/apache2/conf/ssl.crl/
 </code></p></div>
@@ -1273,8 +1269,7 @@ The files in this directory have to be PEM-encoded and are accessed through
 hash filenames. So usually you can't just place the Certificate files
 there: you also have to create symbolic links named
 <em>hash-value</em><code>.N</code>. And you should always make sure this directory
-contains the appropriate symbolic links. Use the <code>Makefile</code> which
-comes with mod_ssl to accomplish this task.</p>
+contains the appropriate symbolic links.</p>
 <div class="example"><h3>Example</h3><p><code>
 SSLProxyCACertificatePath /usr/local/apache2/conf/ssl.crt/
 </code></p></div>
@@ -1359,8 +1354,7 @@ The files in this directory have to be PEM-encoded and are accessed through
 hash filenames. So usually you have not only to place the CRL files there.
 Additionally you have to create symbolic links named
 <em>hash-value</em><code>.rN</code>. And you should always make sure this directory
-contains the appropriate symbolic links. Use the <code>Makefile</code> which
-comes with <code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code> to accomplish this task.</p>
+contains the appropriate symbolic links.</p>
 <div class="example"><h3>Example</h3><p><code>
 SSLProxyCARevocationPath /usr/local/apache2/conf/ssl.crl/
 </code></p></div>
@@ -1523,9 +1517,7 @@ keys used for authentication of the proxy server to remote servers.
 <p>The files in this directory must be PEM-encoded and are accessed through
 hash filenames. Additionally, you must create symbolic links named
 <code><em>hash-value</em>.N</code>. And you should always make sure this
-directory contains the appropriate symbolic links. Use the Makefile which
-comes with mod_ssl to accomplish this task.
-</p>
+directory contains the appropriate symbolic links.</p>
 <div class="warning">
 <p>Currently there is no support for encrypted private keys</p>
 </div>
diff --git a/docs/manual/mod/mod_ssl.xml b/docs/manual/mod/mod_ssl.xml
index f54aa34c9d..88f94f01dd 100644
--- a/docs/manual/mod/mod_ssl.xml
+++ b/docs/manual/mod/mod_ssl.xml
@@ -885,8 +885,7 @@ The files in this directory have to be PEM-encoded and are accessed through
 hash filenames. So usually you can't just place the Certificate files
 there: you also have to create symbolic links named
 <em>hash-value</em><code>.N</code>. And you should always make sure this directory
-contains the appropriate symbolic links. Use the <code>Makefile</code> which
-comes with mod_ssl to accomplish this task.</p>
+contains the appropriate symbolic links.</p>
 <example><title>Example</title>
 SSLCACertificatePath /usr/local/apache2/conf/ssl.crt/
 </example>
@@ -980,9 +979,7 @@ details.</p>
 through hash filenames. So usually you can't just place the
 Certificate files there: you also have to create symbolic links named
 <em>hash-value</em><code>.N</code>. And you should always make sure
-this directory contains the appropriate symbolic links. Use the
-<code>Makefile</code> which comes with mod_ssl to accomplish this
-task.</p>
+this directory contains the appropriate symbolic links.</p>
 <example><title>Example</title>
 SSLCADNRequestPath /usr/local/apache2/conf/ca-names.crt/
 </example>
@@ -1007,8 +1004,7 @@ The files in this directory have to be PEM-encoded and are accessed through
 hash filenames. So usually you have not only to place the CRL files there.
 Additionally you have to create symbolic links named
 <em>hash-value</em><code>.rN</code>. And you should always make sure this directory
-contains the appropriate symbolic links. Use the <code>Makefile</code> which
-comes with <module>mod_ssl</module> to accomplish this task.</p>
+contains the appropriate symbolic links.</p>
 <example><title>Example</title>
 SSLCARevocationPath /usr/local/apache2/conf/ssl.crl/
 </example>
@@ -1496,9 +1492,7 @@ keys used for authentication of the proxy server to remote servers.
 <p>The files in this directory must be PEM-encoded and are accessed through
 hash filenames. Additionally, you must create symbolic links named
 <code><em>hash-value</em>.N</code>. And you should always make sure this
-directory contains the appropriate symbolic links. Use the Makefile which
-comes with mod_ssl to accomplish this task.
-</p>
+directory contains the appropriate symbolic links.</p>
 <note type="warning">
 <p>Currently there is no support for encrypted private keys</p>
 </note>
@@ -1752,8 +1746,7 @@ The files in this directory have to be PEM-encoded and are accessed through
 hash filenames. So usually you can't just place the Certificate files
 there: you also have to create symbolic links named
 <em>hash-value</em><code>.N</code>. And you should always make sure this directory
-contains the appropriate symbolic links. Use the <code>Makefile</code> which
-comes with mod_ssl to accomplish this task.</p>
+contains the appropriate symbolic links.</p>
 <example><title>Example</title>
 SSLProxyCACertificatePath /usr/local/apache2/conf/ssl.crt/
 </example>
@@ -1800,8 +1793,7 @@ The files in this directory have to be PEM-encoded and are accessed through
 hash filenames. So usually you have not only to place the CRL files there.
 Additionally you have to create symbolic links named
 <em>hash-value</em><code>.rN</code>. And you should always make sure this directory
-contains the appropriate symbolic links. Use the <code>Makefile</code> which
-comes with <module>mod_ssl</module> to accomplish this task.</p>
+contains the appropriate symbolic links.</p>
 <example><title>Example</title>
 SSLProxyCARevocationPath /usr/local/apache2/conf/ssl.crl/
 </example>