Hi, I'm new to Camel and got the following problem with Camel 2.6.0:
An HTML file contain an URI lists of files to be downloaded from a web server to the local file system. The HTML file is parsed via a Java Bean Splitter. The Java Bean Splitter produces a Set of URI strings. These files should be downloaded from a web server to the local file system. The extraction and the splitting of the download URIs works quite well with the Java Bean Splitter. The Java Bean Splitter produces URI like http4://download.acme.com/file_1.txt?username=foo&password=baa Here's the setup: http://camel.465427.n5.nabble.com/file/n3424412/Bildschirmfoto_2011-03-11_um_01.54.55.png The injection of the URIs from the Splitter into the HttpProducer, works quite well. I debugged into the HttpProducer and it seems, that the HttpProducer does not provide the unterlying http client (in this case Apache HttpClient 4) with the authentification settings from the URI. When the HttpProducer is assembling the URL from the parts e.g. Endpoint-URI and CamelHttpUri, the authentification parameters are not passed to the underlying http client, see HttpProducer.createMethod(), lines 285-300. At first, the queryString is extracted from the Exchange-Header, if provided. HttpProducer.createMethod(), lines 273. The query string contains the authentification settings as parameters: "username=foo&password=bar" Then a new URI for the requests is assembled from parts of the query string URI and other parameters from the Exchange Header HttpProducer.createMethod(), lines 285-300. The problem is, the assembling of the new URI drops the authentification parameters. Any idea, how to solve my problem? thanks in advance, Hugo -- View this message in context: http://camel.465427.n5.nabble.com/Problem-setting-Authentification-using-HttpProducer-and-dynamic-URIs-tp3424412p3424412.html Sent from the Camel - Users mailing list archive at Nabble.com.
