Jetty adds query parameters as header values

2016-04-21 Thread mluckam
I noticed in the populateRequestParameters function of the DefaultHttpBinding class that query parameters are added as header values in requests. Once this is done then the query parameters continue to exist on the url and also exist as headers which seems redundant. Why are these query parameter

Re: Unable to set Jetty httpClient option

2016-03-19 Thread mluckam
Are you referring to CAMEL-9713 that was fixed with commit 68c6dabca2da2a20bf5ff54ea3061450c91f2c03? If so I see that it allows the HttpClient to be set, but it then appears to ignores additional httpClient.XXX uri options. Is there a reason for this or possibly I am missing something? If not at

Unable to set Jetty httpClient option

2016-03-19 Thread mluckam
I am attempting to set my own httpClient in the url of the camel producer but it does not appear to be taking effect. Looking at the JettyHttpComponent it appears that the endpoint options being set via the URL are extracted in the createEndpoint(String uri, String remaining, Map parameters) funct