Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 31329 invoked from network); 1 Oct 2002 19:27:25 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 1 Oct 2002 19:27:25 -0000 Received: (qmail 27036 invoked by uid 97); 1 Oct 2002 19:28:01 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 26953 invoked by uid 97); 1 Oct 2002 19:27:59 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 26831 invoked by uid 98); 1 Oct 2002 19:27:58 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <3D99F70A.2040408@joedog.org> Date: Tue, 01 Oct 2002 15:27:06 -0400 From: Tim Funk Organization: Human being User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tomcat Developers List Subject: Re: Spec ambiguity? filters and request dispatching References: <20021001190538.90516.qmail@web14304.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N This already has been discussed in the user group in these 2 threads. In a nutshell, tomcat is doing it correctly. But I do find it interesting that websphere and weblogic do differ from tomcat in the same manner with respect to this issue. http://archives2.real-time.com/pipermail/tomcat-users/2002-September/080829.html http://archives2.real-time.com/pipermail/tomcat-users/2002-September/078864.html Eddie Ruvinsky wrote: > The Servlet Spec seems ambiguous about when exactly > the servlet container should invoke filters. Tomcat's > behavior is for a filter to get invoked only when the > request arrives, and before any servlets execute. > However, what should the correct behavior be when a > servlet tries to include or forward a request using > RequestDispatcher to another servlet that is > configured to be "intercepted" by a filter? Tomcat > apparently does not invoke the filter [again] for any > dispatched requests. This is contrary to WebSphere's > interpretation of the spec since it invokes filters > even for dispatched requests (and leaves it up to the > developer to check if the filter is called > "recursively"). This difference in behavior between > servers certainly leads to non-portable applications, > so it should be addressed. > > I'm not sure if this is off-topic for this email > group, but I thought I'd start here since Tomcat is > the reference implementation of the spec. > > Thanks, > -Eddie > -- To unsubscribe, e-mail: For additional commands, e-mail: