[
https://issues.apache.org/jira/browse/CAMEL-10064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15333902#comment-15333902
]
Alexandre Cartapanis commented on CAMEL-10064:
----------------------------------------------
Note that this is only happening with the camel-jetty component in the "to"
endpoint.
This is not happening with camel-http or camel-http4.
> Extra request parameter sent by the camel-jetty component
> ---------------------------------------------------------
>
> Key: CAMEL-10064
> URL: https://issues.apache.org/jira/browse/CAMEL-10064
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
> Affects Versions: 2.16.3
> Reporter: Alexandre Cartapanis
>
> Trying to build a very simple HTTP proxy, exactly like described in the first
> code sample from
> http://camel.apache.org/how-to-use-camel-as-a-http-proxy-between-a-client-and-server.html.
> Using wireshark to see exactly what is going on.
> When i do a request on http://localhost:8080/myapp, the request that is
> sended to real server is
> http://realserverhostname:8090/myapp?bridgeEndpoint=true&throwExceptionOnFailure=false.
> when i do a parameterized request http://localhost:8080/myapp?toto=tata, the
> request that is sended to real server is
> http://realserverhostname:8090/myapp?toto=tata.
> So when the when there is no request param, the endpoint parameter
> bridgeEndpoint=true&throwExceptionOnFailure=false are sended to the
> realserver, and if there is param they are not sended.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
