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 (athena.apache.org: local policy)
From: "Caldarale, Charles R" <Chuck.Caldarale@unisys.com>
To: Tomcat Users List <users@tomcat.apache.org>
Date: Thu, 2 Apr 2009 09:33:05 -0500
Subject: RE: How2 Disable PUT response in OPTIONS method
Thread-Topic: How2 Disable PUT response in OPTIONS method
Thread-Index: AcmzntOYWm//cQUWSPSFKq3/wLwWbwAAM5zw
Message-ID: 
 <0AAE5AB84B013E45A7B61CB66943C17215E6E76F3E@USEA-EXCH7.na.uis.unisys.com>
References: <22786288.post@talk.nabble.com> <49D0EE43.3020602@apache.org>
 <22849145.post@talk.nabble.com>
In-Reply-To: <22849145.post@talk.nabble.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

> From: joeweder [mailto:joeweder@gmail.com]
> Subject: Re: How2 Disable PUT response in OPTIONS method
>=20
> The idea of using a ServletFilter is a good one but
> will not work because the application does not have=20
> a single entry point (dispatch/front-controller)

???  I'm confused; filters are configured in WEB-INF/web.xml, and require n=
o changes to the webapp's servlets.  Why do you think you'd have to modify =
the webapp itself?

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MA=
TERIAL 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 atta=
chments from all computers.


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