-
Notifications
You must be signed in to change notification settings - Fork 38.5k
add support for request body in HTTP DELETE methods using RestClient #32693
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
https://www.rfc-editor.org/rfc/rfc7231#section-4.3.5
Delete with payload is allowed but not recommended. |
hello @quaff and thank you for responding it might not be recommended, but the reality shows there is a need for it → the API from Auth0 - linked in my previous comment - simply requires a payload with a DELETE request this is unfortunately not possible at the moment - which is why I have made a request here in my opinion it should be up to the consumer who makes the request to decide in what way he makes a request and then let a server decide how to respond to it |
Have you tried
That's quite a one-side view of things IMO. Having the spec not recommending this in such terms is a certainly a valid reason for us not exposing a first-class concept for this. Does |
this was also mentioned from quaff before ... what makes you come to this conclusion ?
I don't see anything saying that it's not recommended
now I have and thank you this one works 👍 |
Hello,
currently the RestClient is not supporting request bodies in DELETE requests which is very limiting - especially in cases where additional data beyond URL parameters are needed - such as Remove Roles from Organization Members from Auth0.
Are there any plans to support this in upcoming releases ?
Best regards,
Peter
The text was updated successfully, but these errors were encountered: