We have an OpenAPI v3 JSON that has media types of application/json;charset=UTF8. These are ignored by SwagGen when processing request bodies as it's explicitly looking for application/json or variations thereof with *.
I don't know how valid it is that this additional charset is being specified, the RFC for media types (https://datatracker.ietf.org/doc/html/rfc6838) talks about it in relation to text types only, but it's what we're working with in our automatically generated spec.
We have an OpenAPI v3 JSON that has media types of
application/json;charset=UTF8. These are ignored by SwagGen when processing request bodies as it's explicitly looking forapplication/jsonor variations thereof with*.I don't know how valid it is that this additional charset is being specified, the RFC for media types (https://datatracker.ietf.org/doc/html/rfc6838) talks about it in relation to text types only, but it's what we're working with in our automatically generated spec.