Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of jak-tomcat-user@m.gmane.org
 designates 80.91.229.12 as permitted sender)
To: users@tomcat.apache.org
From: Simon Olofsson <simon@olofsson.de>
Subject: Re: ServletRequestListener and Expect-Header
Date: Mon, 27 Jun 2011 11:06:56 +0200
Lines: 25
Message-ID: <iu9h7p$1rs$1@dough.gmane.org>
References: <4DEFB5BE.20005@olofsson.de>
 <4DF0F136.2070209@christopherschultz.net> <4DF10EED.7020702@ice-sa.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
 rv:1.9.2.17) Gecko/20110516 Thunderbird/3.1.10
In-Reply-To: <4DF10EED.7020702@ice-sa.com>

André,

sorry for my late response.

On 06/09/2011 08:20 PM, André Warnier wrote:
> As I read the API for the ServletRequestListener, I understand that this
> thing is called very early in the cycle.  The spirit seems to be :
> provide a way to warn as soon as possible that a servlet request has
> come in.
> Perhaps even, before we even know that it is really a /HTTP/ servlet
> request.

from [1]:
"A ServletRequest is defined as coming into scope of a web application 
when it is about to enter the first servlet or filter of the web 
application [...]"

So the Listener is only called when this is a valid ServletRequest. The 
Connector ensures that only valid Request are forwarded to the application.

[1] 
http://download.oracle.com/javaee/6/api/javax/servlet/ServletRequestListener.html

Regards
Simon


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