camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adrian Harris <adrian.w.har...@gmail.com>
Subject Re: Using the HTTP4 component to make a HTTPS call behinf proxy sever
Date Thu, 13 Sep 2012 15:57:43 GMT
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: 2.5.29.31 Criticality=false
Unparseable CRLDistributionPoints extension due to
java.io.IOException: invalid URI name:ldap://crl.inov.xxxx.net:389/cn=VI
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: http://camel.465427.n5.nabble.com/Using-the-HTTP4-component-to-make-a-HTTPS-call-behind-proxy-sever-tp5719105p5719311.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Mime
View raw message