summaryrefslogtreecommitdiffstats
path: root/docs/manual/ssl/ssl_faq.html.en
diff options
context:
space:
mode:
authorYoshiki Hayashi <yoshiki@apache.org>2003-06-16 07:32:00 +0200
committerYoshiki Hayashi <yoshiki@apache.org>2003-06-16 07:32:00 +0200
commite46c3e85243728011d632e2e2afbdafcb82b6350 (patch)
tree9b7af57d8d505d32e80a300570367743064f7d33 /docs/manual/ssl/ssl_faq.html.en
parentFix typo. (diff)
downloadapache2-e46c3e85243728011d632e2e2afbdafcb82b6350.tar.xz
apache2-e46c3e85243728011d632e2e2afbdafcb82b6350.zip
Update transformations.
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@100262 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'docs/manual/ssl/ssl_faq.html.en')
-rw-r--r--docs/manual/ssl/ssl_faq.html.en9
1 files changed, 3 insertions, 6 deletions
diff --git a/docs/manual/ssl/ssl_faq.html.en b/docs/manual/ssl/ssl_faq.html.en
index ae97f115cb..5b137899d5 100644
--- a/docs/manual/ssl/ssl_faq.html.en
+++ b/docs/manual/ssl/ssl_faq.html.en
@@ -431,7 +431,7 @@ server Certificate for it. How do I do it?</a></h3>
</a>
</li>
</ol>
- <br />
+
Second you can use your own CA and now have to sign the CSR yourself by
this CA. Read the next answer in this FAQ on how to sign a CSR with
your CA yourself.
@@ -901,15 +901,12 @@ server" What's the reason?</a></h3>
popular that it was already answered a lot of times in the past.
</dd>
<dt>Postings from the modssl-users Support Mailing List
- <a href="http://www.modssl.org/support/">
- http://www.modssl.org/support/</a></dt>
+ <a href="http://www.modssl.org/support/">http://www.modssl.org/support/</a></dt>
<dd>Second search for your problem in one of the existing archives of the
modssl-users mailing list. Perhaps your problem popped up at least once for
another user, too.
</dd>
- <dt>Problem Reports in the Bug Database
- <a href="http://www.modssl.org/support/bugdb/">
- http://www.modssl.org/support/bugdb/</a></dt>
+ <dt>Problem Reports in the Bug Database <a href="http://www.modssl.org/support/bugdb/">http://www.modssl.org/support/bugdb/</a></dt>
<dd>Third look inside the mod_ssl Bug Database. Perhaps
someone else already has reported the problem.
</dd>