Add ability to customize protobuff media type header #613
Conversation
This file contains 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
* Update common files * Update suppressions.xml Co-authored-by: Sergio del Amo <[email protected]>
altro3
force-pushed
the
customize_headers_2
branch
from
c099963
to
53f246d
Compare
|
Thanks for the contribution! |
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.
Sometimes I don't want to give anyone information about my API format and use a custom content-type/accept header value for it. Now you can replace the default ProtobufferCodec and set any media types you want.
I also added a second default media type value, application/protobuf, because it is used by other libraries such as guava.
This is rebased PR (copy of #601), but from master branch