You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue I am seeing is we have a request which allows you to specify Content-Type between x-www-form-urlencoded and multipart/form-data shown below. What I am seeing is that even if I have the content type set to multipart/form-data and attach the csv file is that in the postmanRequest it is setting the content type to x-www-form-urlencoded and does not seem to be attaching the file when the call is made. the ApiExplorer function seems to be getting the item and having it defaulted to x-www-form-urlencoded even though the content type in the dropdown defaults to multipart/form-data even manually selecting from the dropdown does not seem to change the content type.
Expected behavior
I would expect the content-type drop down to change the content type for the postmanRequest and attach the file when making the api call.
Current behavior
The content type seems to only be set to x-www-form-urlencoded and does not attach the file when making the api call.
Possible solution
Steps to reproduce
Screenshots
Context
Your Environment
Version used: we are currently using version 0.0.0-949 with Docusaurus 3.6.3
Environment name and version (e.g. Chrome 59, node.js 5.4, python 3.7.3):
Describe the bug
The issue I am seeing is we have a request which allows you to specify Content-Type between x-www-form-urlencoded and multipart/form-data shown below. What I am seeing is that even if I have the content type set to multipart/form-data and attach the csv file is that in the postmanRequest it is setting the content type to x-www-form-urlencoded and does not seem to be attaching the file when the call is made. the ApiExplorer function seems to be getting the item and having it defaulted to x-www-form-urlencoded even though the content type in the dropdown defaults to multipart/form-data even manually selecting from the dropdown does not seem to change the content type.
Expected behavior
I would expect the content-type drop down to change the content type for the postmanRequest and attach the file when making the api call.
Current behavior
The content type seems to only be set to x-www-form-urlencoded and does not attach the file when making the api call.
Possible solution
Steps to reproduce
Screenshots
Context
Your Environment
The text was updated successfully, but these errors were encountered: