We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Example Swagger/OpenAPI definition:
openapi: 3.0.1 info: title: Test version: 1.0.0 servers: - url: http://localhost:8080 paths: /test: get: responses: "200": description: OK
Swagger-UI configuration options:
SwaggerUIBundle({ url: "https://petstore.swagger.io/v2/swagger.json", dom_id: '#swagger-ui', deepLinking: true, presets: [ SwaggerUIBundle.presets.apis, SwaggerUIStandalonePreset ], plugins: [ SwaggerUIBundle.plugins.DownloadUrl ], layout: "StandaloneLayout", configUrl: "/v3/api-docs/swagger-config", operationsSorter: "alpha", tagsSorter: "alpha", validatorUrl: "" })
Steps to reproduce the behavior:
/test
text/plain;charset=X
I expected the response to be decoded with the charset provided in the Content-Type header.
Content-Type
Works in other clients like Chrome DevTools.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Q&A (please complete the following information)
Content & configuration
Example Swagger/OpenAPI definition:
Swagger-UI configuration options:
Describe the bug you're encountering
To reproduce...
Steps to reproduce the behavior:
/test
and returningtext/plain;charset=X
with a charset other than UTF-8.Expected behavior
I expected the response to be decoded with the charset provided in the
Content-Type
header.Additional context or thoughts
Works in other clients like Chrome DevTools.
The text was updated successfully, but these errors were encountered: