Return-Path: <Costin.Manolache@eng.sun.com>
Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Delivered-To: mailing list tomcat-dev@jakarta.apache.org
Received: (qmail 96004 invoked from network); 20 Jul 2000 18:11:01 -0000
Received: from adsl-63-198-47-229.dsl.snfc21.pacbell.net (HELO costin.dnt.ro)
 (63.198.47.229)
  by locus.apache.org with SMTP; 20 Jul 2000 18:11:01 -0000
Received: from eng.sun.com (costin [63.198.47.229])
	by costin.dnt.ro (8.9.3+Sun/8.9.1) with ESMTP id LAA04596;
	Thu, 20 Jul 2000 11:10:15 -0700 (PDT)
Sender: costin@costin.dnt.ro
Message-ID: <39774291.C00DDC95@eng.sun.com>
Date: Thu, 20 Jul 2000 11:18:57 -0700
From: Costin Manolache <Costin.Manolache@eng.sun.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12-20 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: tomcat-dev@jakarta.apache.org, jemiller@uchicago.edu
Subject: Re: Bug in basic HTTP authentication/resource protection in Tomcat
 3.1?
References: <000001bff266$9c5deb50$0e638780@secns.uchicago.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N

> Jon
>
> P.S. I'm not actually subscribed to this list, so, please CC
> jemiller@uchicago.edu with any responses. Thanks.
>
>       <web-resource-collection>
>          <web-resource-name>Protected Area</web-resource-name>
>   <!-- Define the context-relative URL(s) to be protected -->
>          <url-pattern>/servlet/SnoopServlet</url-pattern>

That's exact map - it protects snoopServlet but doesn't protect
SnoopServlet/

Costin