1
0
-1

I have been able to use the JSON API call (.../jw/web/json/workflow/process/abort/2638_ifcsn_requesterProcess) to sucessfully abort a process using Postman but only if I turn on the option "Follow original HTTP Method." However, if I do the same within my Joget application using Javascript I get the same error that I get in Postman without using that option - "code":"405","message":"Request method 'GET' not supported." I understand this relates to a security modification in the latest HTTP spec. How can I modify the Javascript to POST in the same way as works in the Postman option?

    CommentAdd your comment...

    1 answer

    1.  
      1
      0
      -1

      Hi, there are multiple ways to perform a JavaScript POST, for example using the utility method Javascript API#post(url,callback,params), using JQuery https://api.jquery.com/jquery.post/, or just plain old JavaScript https://stackoverflow.com/questions/9713058/send-post-data-using-xmlhttprequest.


      1. William Vasu

        Anders, please consider the specifics of my question which is why the Joget JSON API does not accept the current standard regarding redirects. I just found the same to be true when sending a POST for the JSON API call http://localhost:8080/jw/web/json/data/form/store/crm/crm_account/001

        It only responds when the Postman option mentioned above is enaabled - "Follow original HTTP Method." If I try to make this JSON API call using a POST within Zapier it does not work. There is no such option in Zapier. Shouldn't the Joget API calls respond to the current standard not a older superceded mode.

        Thanks, Bill

      CommentAdd your comment...