Copied from /java/doc/.

git-svn-id: https://svn.middleware.georgetown.edu/cpp-sp/trunk@689 cb58f699-b61c-0410-a6fe-9272a202ed29

diff --git a/doc/DEPLOY-GUIDE-ORIGIN.html b/doc/DEPLOY-GUIDE-ORIGIN.html
index 7e7051e..8bb8b0d 100644 (file)
--- a/doc/DEPLOY-GUIDE-ORIGIN.html
+++ b/doc/DEPLOY-GUIDE-ORIGIN.html
@@ -204,11 +204,9 @@ configuration, but some older commands have been deprecated or replaced.</p>
     ensure robustness. Failover and redundant configurations are now supported.</li>
     <li>The SHAR may now optionally store its session and attribute cache in a 
     back-end database in addition to the previously available in-memory option.
-    </li>
-&nbsp;<span class="feature">[1.1]</span> </li>
+    <span class="feature">[1.1]</span> </li>
     <li>Federation supplied files (sites.xml and trust.xml) are now refreshed in 
     a much more robust manner. </li>
-    </li>
     <li>The SHAR can be configured to request specific attributes from the 
     Origin. </li>
     <li>The SHAR can use TCP sockets when responding to the Apache module, for 
@@ -333,7 +331,7 @@ that arises. Please ensure that you have the
         </li>
         <li><a href="#5.e."><font color="black">Local Error Page</font></a></li>
         
-        <li><a href="5.f."><font color="black">5.f. Using a New Attribute</font></a></li>
+        <li><a href="#5.f."><font color="black">Using a New Attribute</font></a></li>
         
     </ol>
     </li>
@@ -744,7 +742,7 @@ and <span class="fixedwidth">JSP specification 1.2</span>.</b></p>
             <p><span class="fixedwidth">&lt;Location /shibboleth/AA&gt; 
             <br>&nbsp;SSLVerifyClient optional 
             <br>&nbsp;SSLOptions +StdEnvVars +ExportCertData 
-            &lt;/Location&gt; </span></p>
+                       <br>&lt;/Location&gt; </span></p>
         </blockquote>
         </li>
     </ol>
@@ -1775,7 +1773,7 @@ Java keystores <font color="#5555EE">(optional)</font></h4>
        <p>1. On the java.naming.provider.url Property, add &lt;port number&gt; after the hostname in the ldap url (the default port for ldap over SSL is 636),</p>
        <p>2. Add this Property element:</p>
     <blockquote>
-       <p><span class="fixedwidth">&lt;Property name="java.naming.security.protocol" value="ssl" &quot;&gt;</p>
+               <p><span class="fixedwidth">&lt;Property name="java.naming.security.protocol" value="ssl" &quot;&gt;</span></p>
        </blockquote>
        <p>If the ldap server must be accessed over SSL, and JDK 1.4.2 is being used, then change ldap:// to ldaps:// in the value of the <span class="fixedwidth">java.naming.provider.url</span> Property.</p>
        <p>NOTE: This assumes that the ldap server's cert is rooted with a CA that is in the JVM's default keystore (ie: a commercial CA).  If not, the CA cert must be added.</p>