Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue in request section with postman request always being set to content type x-www-form-urlencoded #1027

Open
darrell-thobe-sp opened this issue Nov 23, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@darrell-thobe-sp
Copy link

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

image

image

image

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):
  • Operating System and version (desktop or mobile):
  • Link to your project: https://github.com/sailpoint-oss/developer.sailpoint.com
@darrell-thobe-sp darrell-thobe-sp added the bug Something isn't working label Nov 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant