Method delete is causing AxiosError about http-request-action HOT 11 OPEN

Hey, thanks for reporting. I will have a look next week

from http-request-action.

from http-request-action.

hm okay, thanks for checking. Sorry I am out of ideas and without testing it myself its hard to find a possible reason.

from http-request-action.

The Status means Not Implemented. I would assume that maybe the URL is not correctly rendered. Did you check if the value of the secret is correct and the ID format? So just want to be sure that its no format error by having for example and additional / in the generated URL. Did you also run the action with enabled debugging to check if everything is setup correctly?

from http-request-action.

Hey

I've copied the non-secret part of URL to Postman and used the same credentials and it worked just right.

I will double-check on my end, but I've copied whole step from working one and changed method from POST to DELETE and changed visible url.

I'm currently bit off grid but when I'm back I will try out local run from binary too.

from http-request-action.

Okay, just wanted to be sure.

I'll check if I see something. But maybe you see something in the logs which looks not as it should.

from http-request-action.

Do you still have issues?

from http-request-action.

Ok I've conducted some tests from runner VM using same key as before:

• GET call just to get some sanity check if I'm running tool correctly ( went fine)

• DELETE call to check what is wrong and it failed
  
  It should return 500 - VM running (due to my oversight)
  

VM was stopped and running from binary returned same 501 error
On the other hand postman worked without any issues

Can I somehow enable logging for the app running from the binary ?

from http-request-action.

Sorry for the late response. The binary does not have more logging right now.

mine thing which came into my mind is that maybe some defaults causing your issue. Like the content type which is set to application json by default. I thing in your working request is no content type set. So you could check if either the content type or default body could be a reason for your server error.

from http-request-action.

Postman by default uses application/json and body is not defined
http-request-action uses application/json and body contains {} by default

cURL generated by postman (I've verified and it works as intended):

curl --location --request DELETE 'XXXX' \ --header 'Content: application/json' \ --header 'Authorization: PVEAPIToken=XX'

from http-request-action.

@fjogeleit No worries. let me know when I can help with the tests.

from http-request-action.