[
https://issues.apache.org/jira/browse/CAMEL-12245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357125#comment-16357125
]
ASF GitHub Bot commented on CAMEL-12245:
----------------------------------------
GitHub user transamericamoon opened a pull request:
https://github.com/apache/camel/pull/2213
CAMEL-12245 Bridged http servlet endpoints should not populate reques…
When you create a servlet endpoint and use the bridgeEndpoint option, the
queryParameters should NOT be put into the exchange headers, because when you
pass this on to the next (http4) endpoint you have the query parameters and an
the same parameters as http headers. So now you are sending additional headers
instead of bridging.
`from("servlet:?matchOnUriPrefix=true&bridgeEndpoint=true")
.to("http4://localhost:8080/testService);`
You can work around this by creating a custom httpBinding, but you should
not have to do this when the connection is bridged.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/transamericamoon/camel CAMEL-12245
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/2213.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2213
----
commit bafbba3c712e93bd3814f14509da967b04c728db
Author: John Moon <john.moon@...>
Date: 2018-02-08T16:04:46Z
CAMEL-12245 Bridged http servlet endpoints should not populate request
parameters into exchange headers
----
> Bridged http servlet endpoints should not populate request parameters into
> exchange headers
> -------------------------------------------------------------------------------------------
>
> Key: CAMEL-12245
> URL: https://issues.apache.org/jira/browse/CAMEL-12245
> Project: Camel
> Issue Type: Bug
> Components: camel-http-common
> Affects Versions: 2.20.2
> Reporter: john
> Priority: Major
>
> When you create a servlet endpoint and use the bridgeEndpoint option, the
> queryParameters should NOT be put into the exchange headers, because when you
> pass this on to the next (http4) endpoint you have the query parameters and
> an the same parameters as http headers. So now you are sending additional
> headers instead of bridging.
>
> example
>
> {code:java}
> from("servlet:?matchOnUriPrefix=true&bridgeEndpoint=true")
> .to("http4://localhost:8080/testService);
> {code}
>
>
> You can work around this by creating a custom httpBinding, but you should not
> have to do this when the connection is bridged.
> WIll submit PR.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
