Open sf-declanomalley opened 1 month ago
If the generated OpenAPI document is essentially the same between the two versions, then this must be an upstream issue with swagger-ui.
You should report the issue in the swagger-api/swagger-ui repo, and we will pick up any fix in a future version.
Describe the bug
in version 6.5 of Swashbuckle.AspNetCore the swashbuckle UI generates a request like the following
however upgrading to 6.6.1 or higher (have upgraded to 6.7.0) the UI generates a request like the following:
as you can see the payload formdata has been tagged as a file. the only difference between the swagger definition between the 2 versions (6.5 and 6.7) is that the response codes changes from "Ok" to "Success" but the requests are very different.
the swagger definition looks like the following.
Expected behavior
request to be the same from the swashbuckle UI for the same swagger definition and generate a form where not specified as binary.
Actual behavior
is sending form data as a file.
Steps to reproduce
pass the swagger definition defined in "Describe the bug" to swashbuckle UI in version 6.5. look at the generated request from developer tools and compare to the request in version 6.7 or swashbuckle.
Exception(s) (if any)
No response
Swashbuckle.AspNetCore version
6.7.0
.NET Version
net8.0
Anything else?
No response