From 0e522dcda802e5a9aebb1c4e471a871de33831aa Mon Sep 17 00:00:00 2001 From: Joe Orton Date: Thu, 3 Jun 2004 10:17:13 +0000 Subject: [PATCH] Update transformation. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@103831 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/ssl/ssl_compat.html.en | 70 ++++++++++++++---------------- 1 file changed, 32 insertions(+), 38 deletions(-) diff --git a/docs/manual/ssl/ssl_compat.html.en b/docs/manual/ssl/ssl_compat.html.en index 40e19a8dd5..3fde38e090 100644 --- a/docs/manual/ssl/ssl_compat.html.en +++ b/docs/manual/ssl/ssl_compat.html.en @@ -28,22 +28,24 @@ them are more compatible than others.

-Here we talk about backward compatibility to other SSL solutions. As you -perhaps know, mod_ssl is not the only existing SSL solution for Apache. -Actually there are four additional major products available on the market: Ben -Laurie's freely available Apache-SSL -(from where mod_ssl were originally derived in 1998), Red Hat's commercial Secure Web -Server (which is based on mod_ssl), Covalent's commercial Raven SSL Module (also based on mod_ssl) -and finally C2Net's commercial product Stronghold (based on a -different evolution branch named Sioux up to Stronghold 2.x and based on -mod_ssl since Stronghold 3.x).

+This page covers backwards compatibility between mod_ssl and other +SSL solutions. mod_ssl is not the only SSL solution for Apache; four +additional products are (or were) also available: Ben Laurie's freely +available Apache-SSL (from +where mod_ssl were originally derived in 1998), Red Hat's commercial +Secure +Web Server (which was based on mod_ssl), Covalent's commercial Raven SSL Module (also based on +mod_ssl) and finally C2Net's (now Red Hat's) commercial product Stronghold (based +on a different evolution branch named Sioux up to Stronghold 2.x and +based on mod_ssl since Stronghold 3.x).

-The idea in mod_ssl is mainly the following: because mod_ssl provides mostly a -superset of the functionality of all other solutions we can easily provide -backward compatibility for most of the cases. Actually there are three -compatibility areas we currently address: configuration directives, -environment variables and custom log functions.

+mod_ssl mostly provides a superset of the functionality of all other +solutions, so it's simple to migrate from one of the older modules to +mod_ssl. The configuration directives and environment variable names +used by the older SSL solutions vary from those used in mod_ssl; +tables are included here to give the equivalents used by mod_ssl to +allow easy migration. .