DELETE endpoints cannot have a body about rest.vertx HOT 4 CLOSED

On Tue, 5 Mar 2019 at 17:51, Fabian Iffländer ***@***.***> wrote: Wow! That was fast :) Do you plan a bugfix release? — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#42 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABsql6t7fB37WbCvgBPn2_Ry6vqYuO71ks5vTqB6gaJpZM4be8hD> .

On Tue, 27 Aug 2019 at 00:57, jsirach ***@***.***> wrote: Good evening, I've seen the issue has been closed, but i'm seeing some odd behavior. Using vertx web 3.8.0, updated rest.vertx to 0.8.9. I'm having one path with a GET and a DELETE 1: @get <https://github.com/get> @path <https://github.com/path>("tokens/:tokenReferenceId") 2: @delete <https://github.com/delete> @path <https://github.com/path>("tokens/:tokenReferenceId") I'm noticing after the update the DELETE annotated method is results in a 404. But after adding an empty body to my delete request, the DELETE annotated method is found again. It looks like DELETE now requires a body to be able to be identified. For now for me it's not a problem because my calls are made generic in my front-end, so adding an empty object is not that big of a deal. But it was unexpected. You want me to open a new report? — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#42?email_source=notifications&email_token=AANSVF7Y7RDKNVZRJTTE24DQGRNVXA5CNFSM4G33ZBB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5F5VOI#issuecomment-525064889>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AANSVF4VXNCFCBV4UCWVU63QGRNVXANCNFSM4G33ZBBQ> .