fix: support non-standard MIME type in response header #2124
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MaggieKimani1
requested review from
andrueastman,
baywet,
darrelmiller,
gavinbarron,
irvinesunday and
millicentachieng
as code owners
MaggieKimani1
changed the title
Merged
…g a new exception instance
baywet
requested changes
Feb 5, 2025
baywet
approved these changes
Feb 5, 2025
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1989 where the document's format was not being correctly set for non-standard MIME types when inspecting the content type header in a HTTP response object.
E.g. the MIME type
text/x-yamlwhich is still in use by older libraries or APIs