In Tenjin HTTP flow step we have a number of pre-defined content-types in a drop down list for the body passed into a POST. Some APIs do not fit these content-type definitions and thus fail when passing a valid body. In both the following examples, the content returned from the calls would normally be valid JSON:
NSS API post for token expects 'application/x-www-form-urlencoded', returns JSON.
Nexthink API expects 'application/json', returns JSON. Passing 'application/json; charset=utf-8', as specified in drop down, fails.
Would it be possible to allow custom content-type for POST body submissions to allow any content-type to be passed in - e.g. a textbox? This would potentially open things up to many more legacy APIs.
This was completed in #3357 at the end of 2021 with the following ToDo item:
[Done] If a Content-Type Header is added to the action use that value, instead of the selected Content Type from the dropdown
Related Dev stories:
Flow - Support more POST content types
Allow content type of 'application/json' without 'charset'
Maybe the simplest approach would be to allow the main headers to override the drop down - i.e. if I enter Content-Type as an explicit header, it takes priority and ignores the drop down.