Netty provider: Support multi-valued headers in Request #403
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
|
You're right that this should support multi value headers. However, I'm not fond of |
|
@lukiano Actually, the problem was a bit more complex: user provided headers can be multi valued, but some have to be fully overridden. Thanks for reporting! |
ghost
assigned
|
You're welcome! Do you have an estimate for 2.0 release? |
|
No, sorry. There's still a lot of refactoring to be done on the Netty provider. |
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.
In one step of the request process, the headers are saved in a regular map, instead of a multi-value map like everywhere else. This pull request fixes that.