Return-Path: 
 <users-return-223431-apmail-tomcat-users-archive=tomcat.apache.org@tomcat.apache.org>
Delivered-To: apmail-tomcat-users-archive@www.apache.org
Received: (qmail 70306 invoked from network); 1 Apr 2011 15:47:59 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 1 Apr 2011 15:47:59 -0000
Received: (qmail 59704 invoked by uid 500); 1 Apr 2011 15:47:56 -0000
Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org
Received: (qmail 59530 invoked by uid 500); 1 Apr 2011 15:47:55 -0000
Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@tomcat.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@tomcat.apache.org>
List-Post: <mailto:users@tomcat.apache.org>
List-Id: <users.tomcat.apache.org>
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Delivered-To: mailing list users@tomcat.apache.org
Received: (qmail 59521 invoked by uid 99); 1 Apr 2011 15:47:55 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Apr 2011 15:47:55 +0000
X-ASF-Spam-Status: No, hits=0.0 required=5.0
	tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of eric.cha.read@gmail.com
 designates 209.85.220.173 as permitted sender)
Received: from [209.85.220.173] (HELO mail-vx0-f173.google.com)
 (209.85.220.173)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Apr 2011 15:47:48 +0000
Received: by mail-vx0-f173.google.com with SMTP id 41so4101512vxb.18
        for <users@tomcat.apache.org>; Fri, 01 Apr 2011 08:47:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:message-id:date:from:user-agent:mime-version:to
         :subject:references:in-reply-to:content-type
         :content-transfer-encoding;
        bh=XM/hIF9xxpuNXD3DG/B4bkRHU1h2ZGEjMLqf45YHccg=;
        b=NOjPNwuGqq0jB5/cQC6Yybhk8f7LRvyrL7WtkpeGhq9F1Pa7HUj1PELqaWrK4TOxqF
         DsJKy0Odq0H3U5gh6QwHjCYJjGGov5oDWifOEEaUPyOF9LYKYeZq31edZlrF9BjmMWyx
         Q74BjNOKOC0/V2Q6sesgPOU6qNy01m9R0BhRo=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        b=Q8NfLwmmnEJp7TyStdzIM7Yc2p3eg4udXTt+o2YflypuGjnSne8+/HcZrxqzUvcgNi
         u8tEvKE25E8vRP+S3VvTDGkQ9l3mhSIclhBblNS5lgczEqELPeKz+5efNaBBORoHfMEh
         v+kTtM6FO0TzhMROTssB48ElXqKpKAMMMAvl0=
Received: by 10.52.67.105 with SMTP id m9mr504887vdt.126.1301672847760;
        Fri, 01 Apr 2011 08:47:27 -0700 (PDT)
Received: from [192.168.8.170] ([108.6.67.30])
        by mx.google.com with ESMTPS id b24sm1249442vby.7.2011.04.01.08.47.26
        (version=SSLv3 cipher=OTHER);
        Fri, 01 Apr 2011 08:47:27 -0700 (PDT)
Message-ID: <4D95F38E.6060408@gmail.com>
Date: Fri, 01 Apr 2011 11:47:26 -0400
From: Cha <eric.cha.read@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
 rv:1.9.2.14) Gecko/20110223 Thunderbird/3.1.8
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: url-pattern algorithm problem?
References: <4D95ED1D.9070203@gmail.com>
 <99C8B2929B39C24493377AC7A121E21FACD8F9A7B7@USEA-EXCH8.na.uis.unisys.com>
In-Reply-To: 
 <99C8B2929B39C24493377AC7A121E21FACD8F9A7B7@USEA-EXCH8.na.uis.unisys.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

My bad, the app is deployed as 'ROOT' and I did read the url-pattern 
section in the section before posting the question.

Based on what I read, it should match to the 'app', but it is not in 
this case.

Cha.

On 04/01/2011 11:39 AM, Caldarale, Charles R wrote:
>> From: Cha [mailto:eric.cha.read@gmail.com]
>> Subject: url-pattern algorithm problem?
>> <url-pattern>*.htm</url-pattern>
>> <url-pattern>/en/*</url-pattern
>> The problem we find if the incoming url is like
>> "http://example.com/en/yp/list/cat/10/1", it will
>> not matched to the 'app' servlet.
> Likely correct behavior, since neither of your specified patterns match the incoming URL - if your webapp is deployed as "en".  The above pattern would only match the URL if your webapp is deployed as "ROOT" - but you didn't tell us.
>
>> Could it be a problem in tomcat matching algorithm?
> Read the servlet spec; the<url-pattern>  does *not* include the context (webapp) name.
>
>   - Chuck
>
>
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org