Which version of camel are you using? You can setup the authentication information through the URI option at the mean time.
-- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On August 12, 2014 at 11:26:58 PM, rickaroni (rgfa...@directv.com) wrote: > [Sorry, some comments got stripped out of the posting. The first call that > tries to use the HttpComponent fails; the 2nd call that provides basic auth > params in simple-recipientList succeeds.] > > Thanks for the reply. I tried your suggestion but it doesn't seem to work > for me. > > This: > > > > > > > > > *https2*://${in.headers[MY_SERVER_AND_PORT]}/rest/accounts/account/${in.headers[ACCOUNT_NUMBER]}/doSomethingToMyAccount > > > > results in the following: > > org.apache.camel.component.http.HttpOperationFailedException: HTTP operation > failed invoking > http:///rest/accounts/account//doSomethingToMyAccount > with statusCode: 302, redirectLocation: > https:///rest/accounts/account//doSomethingToMyAccount > > and the basic auth parameters are never recognized after the redirect. > > In both cases, the recipientList + simple combination don't seem to want to > accept the auth parameters in the HttpComponent. > > I'm trying to do the auth config on each of the two http configurations in > the route instead of doing it on the component because the requirements are > different. > > Many thanks once again for any suggestions you can offer. > > Rick > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/How-can-I-make-a-RecipientList-http-component-use-an-HttpConfiguration-tp5755116p5755121.html > > Sent from the Camel - Users mailing list archive at Nabble.com. >
