For additional commands, e-mail: users-h...@tomcat.apache.org
--
View this message in context:
http://www.nabble.com/How2-Disable-PUT-response-in-OPTIONS-method-tp22786288p22849145.html
Sent from the Tomcat - User mailing list archive at Nabble.com
joeweder wrote:
Thanks markt-2. The idea of using a ServletFilter is a good one but will not
work because the application (we've inherited) does not have a single entry
point (dispatch/front-controller) yuck. So I'd have to patch it several
places.
You can map filters to /*
Mark
What I
From: joeweder [mailto:joewe...@gmail.com]
Subject: Re: How2 Disable PUT response in OPTIONS method
The idea of using a ServletFilter is a good one but
will not work because the application does not have
a single entry point (dispatch/front-controller)
??? I'm confused; filters
.
Is there any way to get Tomcat 6 from responding to the OPTIONS that it
supports the PUT?
--
View this message in context:
http://www.nabble.com/How2-Disable-PUT-response-in-OPTIONS-method-tp22786288p22786288.html
Sent from the Tomcat - User mailing list archive at Nabble.com
joeweder wrote:
I have PUTs disabled but they are still being published as supported in
response to the OPTIONS method.
Which is correct as per the HTTP spec.
Allow: GET, HEAD, POST, PUT, DELETE, TRACE, OPTIONS
Server: Apache-Coyote/1.1
Actually doing a PUT returns a 403. But in-house
