[
https://issues.apache.org/jira/browse/CAMEL-12245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
john updated CAMEL-12245:
-------------------------
Description:
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
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.
was:
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.
> 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
> 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)
