> 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'
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
>
> Wha
method.
>
> Alternatively, you should be able to achieve the same effect with a Filter
> and a
> wrapped response.
>
> Mark
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
&
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-hou
he OPTIONS method.
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
