Wildcard content-type "*/*" leads to unparsed JSON responses

[ahx]

Currently openapi_first picks a response parser based on the content-type defined in your OAD. If you specify a content-type like application/json: your response will be parsed with JSON.

When your OAD has a response content-type specified like */* openapi_first current does not parse the response body at all and just returns the plain body (as a String).

This leads to having a response definition like this always failing validation, because a the string (String) is not an object (Hash):

          content:
            "*/*":
              schema:
                type: object

[ahx]

This is because while reading through an OAD, openapi_first creates Response instances, that each match the given content-type and have one instance of a body-parser. The default body-parser just returns the plain body. During request validation openapi_first looks which of the Response instances matches the content-type of the incoming response. It finds the Response instance with the default body parser and returns a string to be validated.

To make a response content-type definition like "/" parse a JSON respose we would need to change ResponseParser to look at the actual response content-type and lookup a matching parser during runtime.