On 26/12/2023 12:00, koteswara Rao Gundapaneni wrote:
HTTP Patch option should be deprecated as the option is doing partial
changes to an existing resource.
PATCH is a method, not an option. Using the correct terminology is
important to avoid confusion. Especially when OPTIONS is also a method.
Support for PATCH is an Jakarta Servlet project decision, not a Tomcat
project decision. Wearing my Tomcat committer hat, I agree that PATCH
should be supported.
Note that PATCH is only supported if a Servlet explicitly implements
support for PATCH.
combination of the options and trace methods works very well rather than
the Http PATCH
Wrong. PATCH enables modification. Neither TRACE nor OPTIONS nor a
combination of TRACE and OPTIONS enable modification.
It works very well when the jsperror page is redirected as it shown trace
option
The above sentence makes no sense.
private String getCachedAllowHeaderValue() {
<snip/>
Please do not quote extensive blocks of existing code. It is pointless.
If you want to propose a patch, do so via Bugzilla or submit a PR via
GitHub.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
