Closed jonathanberthias closed 6 months ago
Attention: Patch coverage is 90.00000%
with 1 lines
in your changes are missing coverage. Please review.
Project coverage is 90.26%. Comparing base (
9268452
) to head (fb0ea95
). Report is 11 commits behind head on master.
Files | Patch % | Lines |
---|---|---|
openapi_core/templating/media_types/finders.py | 90.00% | 0 Missing and 1 partial :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
@jonathanberthias thanks for the contribution.
Currently, the Content-Type header splits the media type from the parameters by looking for
;
(a semicolon followed by a space), whereas according to RFC 9110 that space is optional.This leads to issues when a client sends e.g.
application/json;charset=utf-8
which is valid as a Content Type header.I used the examples from the RFC and made sure they are correctly handled. It isn't a full coverage of the allowed grammar, but hopefully it should cover most use cases.