From 5221951ddf7744c0396db67f95b22e946eb6e25f Mon Sep 17 00:00:00 2001 From: maxcooper Date: Wed, 14 Aug 2002 17:36:19 +0000 Subject: [PATCH] removed url-pattern comment and fixed two step 2s issue --- README | 14 +++++--------- 1 file changed, 5 insertions(+), 9 deletions(-) diff --git a/README b/README index 66f6208..9efb97a 100644 --- a/README +++ b/README @@ -1,6 +1,6 @@ -$Id: README,v 1.5 2002/08/14 11:26:31 maxcooper Exp $ -$Revision: 1.5 $ -$Date: 2002/08/14 11:26:31 $ +$Id: README,v 1.6 2002/08/14 17:36:19 maxcooper Exp $ +$Revision: 1.6 $ +$Date: 2002/08/14 17:36:19 $ Security Filter v1.0-b2-dev @@ -64,7 +64,7 @@ first realm specified in the config file (described below) need implement the SecurityRealmInterface interface -- there are no type restrictions for realms that will be adapted. -2. Declare your security preferences in WEB-INF/securityfilter-config.xml. The +3. Declare your security preferences in WEB-INF/securityfilter-config.xml. The format for security preferences closely mimics the web.xml standard (so you can but and paste if you have been using container-managed security). In addition to the web.xml syntax, you can also specify a form-default-page to send users to if @@ -83,11 +83,7 @@ apps. Compliance with the servlet 2.3 spec is a top priority for the project, but it is not 100% compliant yet. There are a few things that are not yet supported that may be important to you: -1. Requests are evaluated against the url-patterns in the order that the -patterns appear in the config file, rather than by the rules defined in the -servlet spec. - -2. user-data-constraint tags can be included in the config file, but they are +1. user-data-constraint tags can be included in the config file, but they are not yet supported (and thus are ignored) -- 2.11.0