Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Allow Composer to send a HTTP request using non-json body
See original GitHub issueBackground
I’d like to be able to HTTP POST non-json data. Right now I am constrained to json-only.
As an example I’d like to POST application/x-www-form-urlencoded to request an access token from Azure AD.
Currently the validation stops me from saving this:
Ideally, this would save without validating the input and make it the responsibility of the person composing the conversation to get it right. Alternatively, if it is necessary to validate, have a dropdown to select the Content-Type similarly to postman/fiddler where you can choose from form-data, x-www-form-urlencoded, json, raw.
Current workaround
I am working around this by proxying the request to Azure AD with a custom API which accepts json input and the Composer/ Adaptive Dialog can connect through to.
Issue Analytics
- State:
- Created 4 years ago
- Comments:19 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@mg-arrow sorry for the late response, composer already updated the sdk package to 4.10.0, you can try with the latest main branch.
Does anyone know how to get this body of type “multipart/form-data” to work in Bot Composer? I have tried so many combinations but couldn’t get this to work. And I couldn’t find any suitable answer either.
