v3.2 Respect encoding in all Media Type Objects
#4559
Merged
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
There is no reason to restrict use of the `encoding` field of the Media Type Object to Request Body Objects only. Not only does this exclude legitimate use cases of returning multipart content (particularly as we fix the support for `multipart/mixed`), it also complicates implementation by requiring the handlingn of the Media Type Object to be context-aware. This is a rare change that both simplifies implementation and adds functionality.
handrews
added
the
media and encoding
This removes request body-specific wording where it was present.
lornajane
approved these changes
May 1, 2025
|
For posterity, the use case for this most recently came up in an API that provides a streaming multipart json response. Somewhere I know this "request body only" restriction came up in an older issue but I cannot find it now. |
3 tasks
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.
There is no reason to restrict use of the
encodingfield of the Media Type Object to Request Body Objects only. Not only does this exclude legitimate use cases of returning multipart content (particularly as we fix the support formultipart/mixed), it also complicates implementation by requiring the handling of the Media Type Object to be context-aware.This is a rare change that both simplifies implementation and adds functionality.