-
Notifications
You must be signed in to change notification settings - Fork 8.8k
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
Not able to decode multipart response #5293
Comments
Hi SachidanandAlle, did you get an answer on this? I'm having exactly the same issue. |
No.. as a workaround (to unblock), I had to support additional flag at my server side to send/download binary or text/json only data in the response. Basically you will trigger copy of requests for each form type expected in the response. (Not a good idea) It shall be great if Swagger UI can do parse the multi-response object and support different schema for each type. |
Thanks for you quick answer SachidanandAlle, yes it's a pitty, and it's strange that the Swagger UI and codegen is not able yet to handle these kind of responses. |
Much needed feature as API client. |
Hi! Happy to finally find people who have the same issue :D |
Hi! Any updates on this issue? |
Q&A (please complete the following information)
Content & configuration
Fails to decode the response when it is of multipart type.
Example Swagger/OpenAPI definition:
Describe the bug you're encountering
When the UI receives the response from the server where the response has multipart body, the UI doesn't decode the message and displays the result accordingly.
Currently it shows the following error and tries to display everything as text (even the binary junk characters) and the multipart data is not split into corresponding part files.
Response body
Unrecognized response type; displaying content as text.
Expected behavior
The text was updated successfully, but these errors were encountered: