fix filtering content-type and content-length headers in HttpClientBa… #2135
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.
Before submitting pull request:
sbt compile
sbt compileDocs
sbt test
sbt scalafmt
Problems
The java HttpClient prohibits to add
Content-Type
header to request, it's reason HttpClientBacked filters this header. But the check is case-sensitive. So passingcontent-type
(in lower case) header occurs IllegalArgumentException.Another problem is duplicating
content-type
header inside request if the header name passed in lowercase.These problems might happen if an application gets these headers from an incoming HTTP request and then pass them to a new HTTP request to another service.