Hi
You can also set the ssl contenxt parameters once globally on the
http4 component and then you dont need thats in the endpoint uris.
On Wed, Feb 6, 2019 at 6:36 AM Claus Ibsen <claus.ib...@gmail.com> wrote:
>
> Try with 2.22.3 or 2.23.1 release
>
> On Fri, Feb 1, 2019 at 7:09 PM Greg Ludington <gluding...@gmail.com> wrote:
> >
> > We are attempting to update to 2.22.2, and have a problem with dynamic
> > URLs, specifically those involving sslContextParameters. To use an
> > example, a flow would have this:
> >
> > <camel:toD
> > uri="https4://${property.hostName}/${property.path}/${property.serviceName}?sslContextParameters=#sslContextParameters&throwExceptionOnFailure=false"/>
> >
> > Prior to the 2.22 series, this would work. In 2.22, however, the
> > sslContextParameters are not added to the call, resulting in the
> > typical PKIX path building failed error when trying to hit any SSL
> > service. Using a camel:to instead of a camel:toD works fine.
> >
> > Unfortunately, setting header properties and changing to a camel:to from a
> > toD, assuming that approach were to work, is likely going to be met with
> > serious resistance, as most flows spread out among client instances utilize
> > this pattern. Is there there any ticket on this issue, or release where
> > that particular syntax may be addressed to work as it did previously?
> >
> > Thanks,
> > Greg
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
