camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Willem Jiang <>
Subject Re: Using the HTTP4 component to make a HTTPS call behinf proxy sever
Date Fri, 14 Sep 2012 02:25:20 GMT
No, I dont think the upgrading can resolve the issue, as there is no
much chang in the camel-http4 component.   Can you try to invoke the
sevice by using http client4 directly?

2012/9/13, Adrian Harris <>:
> Hi,
> Thanks for the response, the workaround was a success.
> I now have an additional problem further down the line with the handshake
> which I believe is not camel related. I get the error
> Unparseable certificate extensions: 1
> [1]: ObjectId: Criticality=false
> Unparseable CRLDistributionPoints extension due to
> invalid URI name:ldap://
> CA2,c=US,ou=xxxx xxxxxxxxx xxxxxxxxx
> xxxxxxx,o=xxxx?certificateRevocationList
> The certificate is provided to us by a third party and the failure is on
> parsing their response from the handshake. I have xxxx the company
> identifying info from the uri but the format is the same
> I assume there is a problem with their certificate or service but does
> anyone know a way to ignore this error? I did read that upgrading to
> HTTPClient 2.x may resolve it but I don't think you can do that with Camel
> 2.10.1?
> Thanks
> Adrian
> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at

View raw message