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
I've noticed that the source code doe does not properly register the response validator if an operation's content type is defined with the charset identifier, such as
content:
application/json; charset=UTF-8:
The issue seems to be line 438 of node_modules/openapi-backend/validation.js, where it simply checks to see if the content is application/json, this missing an application/json with a charset identifier.
As far as I can tell, neither the JSON spec nor the Media Type spec allow the usage of the "charset" parameter together with "application/json", so that would mean your example is part of an invalid OpenAPI document. For a better argumentation see axios/axios#2154 (comment) and request/request#383.
I've noticed that the source code doe does not properly register the response validator if an operation's content type is defined with the charset identifier, such as
The issue seems to be line
438
ofnode_modules/openapi-backend/validation.js
, where it simply checks to see if the content isapplication/json
, this missing anapplication/json
with a charset identifier.The text was updated successfully, but these errors were encountered: