GitHub user kdombeck opened a pull request:
https://github.com/apache/tomcat/pull/96
Remove PUT and DELETE methods from an OPTIONS request if readOnly is true
Currently ```DefaultServlet``` is returning all HTTP methods for an OPTIONS
call even when the **readOnly** flag is true
Github user kdombeck commented on the issue:
https://github.com/apache/tomcat/pull/96
Thanks for the quick responses.
I modeled this change after the changes for TRACE in the next if statement
below. Also looking at
[issue](https://bz.apache.org/bugzilla/show_bug.cgi?id
Github user kdombeck commented on the issue:
https://github.com/apache/tomcat/pull/96
I started this
[thread](http://tomcat.10.x6.nabble.com/Change-HTTP-status-code-for-DefaultServlet-with-readOnly-set-to-true-td5070373.html)
on the mailing list to look for consensus.
If
Github user kdombeck commented on the issue:
https://github.com/apache/tomcat/pull/96
I haven't had any responses in
[thread](http://tomcat.10.x6.nabble.com/Change-HTTP-status-code-for-DefaultServlet-with-readOnly-set-to-true-td5070373.html)
I started for this issue.
I
Github user kdombeck commented on the issue:
https://github.com/apache/tomcat/pull/96
@michael-o I don't understand your question. Are you asking why ```PUT```
and ```DELETE``` are not allowed when the **readOnly** flag is true but
```POST``` is al
Github user kdombeck commented on the issue:
https://github.com/apache/tomcat/pull/96
@michael-o I had the exact same question in my original post. The only
thing I saw was that the POST delegates to the GET, so they both have the same
effect
Github user kdombeck commented on the issue:
https://github.com/apache/tomcat/pull/96
@markt-asf I haven't received any responses to the
[thread](http://tomcat.10.x6.nabble.com/Change-HTTP-status-code-for-DefaultServlet-with-readOnly-set-to-true-td5070373.html)
I started on de
