----- Original message -----
From: Pavel Bucek <pavel.bucek@oracle.com>
To: users@jax-rs-spec.java.net
Cc:
Subject: [jax-rs-spec users] Re: Native support for additional HTTP methods
Date: Wed, Apr 5, 2017 7:21 AM
Hi Andrew,
I added 2.1-candidate tag to an issue which suggests adding PATCH method and content type.
I'm not exactly sure how should an application handle TRACE request - isn't that something which should be handled by the underlying container?
CONNECT is similar - what would be the usecase of handing that from JAX-RS application? (I believe I'm not the only one who is not considering implementing HTTP proxy as a valid usecase for REST API to support).
Thanks and regards,
PavelOn 04/04/2017 22:32, Andrew McCright wrote:
Hi All,We've seen a number of requests from our customers for built-in support of other HTTP methods such as CONNECT, TRACE, and PATCH -- PATCH has been especially requested.While it is currently possible for users to define their own custom HTTP methods, I've seen a few support cases where users are not implementing them properly - for example, one customer did not safely implement a PATCH method for case sensitivity, so when a client sent a "patch" request, they ended up with a 415.What would you think about adding these methods as annotations in the spec?Thanks,Andy