jorton 2004/06/03 03:16:12 Modified: docs/manual/ssl ssl_compat.xml Log: Fix links and update content in introduction. Update page content to reflect that mod_ssl in 2.0 doesn't actually provide the most of the backwards-compat hooks; leave it as a guide for migration. Revision Changes Path 1.11 +36 -43 httpd-2.0/docs/manual/ssl/ssl_compat.xml Index: ssl_compat.xml =================================================================== RCS file: /home/cvs/httpd-2.0/docs/manual/ssl/ssl_compat.xml,v retrieving revision 1.10 retrieving revision 1.11 diff -d -w -u -r1.10 -r1.11 --- ssl_compat.xml 17 Apr 2004 11:18:05 -0000 1.10 +++ ssl_compat.xml 3 Jun 2004 10:16:12 -0000 1.11 @@ -32,37 +32,35 @@
-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. .
For backward compatibility to the configuration directives of other SSL -solutions we do an on-the-fly mapping: directives which have a direct -counterpart in mod_ssl are mapped silently while other directives lead to a -warning message in the logfiles. The currently implemented directive mapping -is listed in Table 1. Currently full backward -compatibility is provided only for Apache-SSL 1.x and mod_ssl 2.0.x. -Compatibility to Sioux 1.x and Stronghold 2.x is only partial because of -special functionality in these interfaces which mod_ssl (still) doesn't -provide.+
The mapping between configuration directives used by Apache-SSL +1.x and mod_ssl 2.0.x is given in Table +1. The mapping from Sioux 1.x and Stronghold 2.x is only partial +because of special functionality in these interfaces which mod_ssl +doesn't provide.
When you use ``
SSLOptions +CompatEnvVars'' additional environment
-variables are generated. They all correspond to existing official mod_ssl
-variables. The currently implemented variable derivation is listed in The mapping between environment variable names used by the older
+SSL solutions and the names used by mod_ssl is given in Table 2.
-When mod_ssl is built into Apache or at least loaded (under DSO situation)
-additional functions exist for the Custom Log Format of