From: maxcooper <maxcooper>
Date: Mon, 19 Aug 2002 22:08:57 +0000 (+0000)
Subject: Fixed typo: you --> your
X-Git-Tag: REL-1_0_b3~2
X-Git-Url: https://git.internetallee.de/?a=commitdiff_plain;h=c6ada900d44487e1b3f37148c7d7c1f8a86a05ec;p=securityfilter.git

Fixed typo: you --> your
---

diff --git a/doc/index.html b/doc/index.html
index 15368ea..5050c6c 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -43,7 +43,7 @@ SecurityFilter is intended for use by Java web application developers. It provid
 <h2>Advantages of SecuirtyFilter over Container Managed Security:</h2>
 
 <ul>
-  <li>Security Filter is intended to be packaged within your web app, including your realm implementation and supporting classes. This allows you to deploy you app as a single, deployable unit (war file or expanded war directory structure) with no additional configuration of the server environment. This is in contrast to container managed security in which the realm must be added to the server's classpath (including any supporting classes) and configured in the server.<p /></li>
+  <li>Security Filter is intended to be packaged within your web app, including your realm implementation and supporting classes. This allows you to deploy your app as a single, deployable unit (war file or expanded war directory structure) with no additional configuration of the server environment. This is in contrast to container managed security in which the realm must be added to the server's classpath (including any supporting classes) and configured in the server.<p /></li>
   <li>Security Filter supports &quot;unsolicited&quot; login requests, and will send the user to a destination you have configured upon successful authentication. This allows you to have a login form on every page, or simply link directly to your login form to authenticate users. With container managed security, the container will not process login requests unless the container itself has initiated the authentication sequence (i.e. sent the user to the login form) in response to a request for a protected resource, which makes it impossible to have a login form on every page and complicates implementation of a link to the login form.<p /></li>
   <li>Each server has its own realm interface, so your realm implementation will not be portable across different servers. Security Filter has a small, simple realm interface that is portable across different servers (because it is proprietary to Security Filter rather than the server implementation). Security Filter also supports adapter classes to adapt a proprietary realm implementation from any server to the Security Filter realm interface, which will get you up and running quickly and makes your realm portable across different server implementations. A Tomcat/Catalina realm adapter is included in the package now, adapters for other realm implementations are planned, and it is easy to implement your own adapter by following the Catalina realm adapter as an example.<p /></li>
 </ul>