ASF GitHub Bot commented on CAMEL-12245:

transamericamoon commented on issue #2213: CAMEL-12245 Bridged http servlet 
endpoints should not populate reques…
URL: https://github.com/apache/camel/pull/2213#issuecomment-364463877
   Thanks Claus, my mistake.  We are trying to change all of our restlet 
endpoints to http4 endpoints to simplify things.  I think for some reason in 
the old camel-restlet some of our headers did not get mapped...
   The restlet base library is becoming a mess, where http4 is very simple and 
clean. For example: 
   Thanks for the help.

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> 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

Reply via email to