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
swagger: "2.0"
info:
version: ""
title: test
schemes:
- http
paths:
/fragment:
get:
produces:
- text/html
description: returns some html
responses:
200:
description: text/html response
schema:
type: string
HippieSwagger 3.2.0 chokes on the response, as it assumes all responses to always be JSON - but can't parse HTML as JSON. Can the JSON-parsing be disabled somehow?
I'm facing a similar issue (albeit when a service returns 500 instead of the expected response code). Having this be parsed properly would reduce effort in to debugging failures
Given Swagger:
HippieSwagger 3.2.0 chokes on the response, as it assumes all responses to always be JSON - but can't parse HTML as JSON. Can the JSON-parsing be disabled somehow?
Specification for Swagger 2.0 concerning mime-types in requests and responses:
https://swagger.io/docs/specification/2-0/mime-types/
The text was updated successfully, but these errors were encountered: