camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Willem jiang <willem.ji...@gmail.com>
Subject Re: Using the HTTP4 component to make a HTTPS call behinf proxy sever
Date Wed, 12 Sep 2012 06:05:38 GMT
Hi

I'm assume your proxy is not using ssl, I just checked the code of camel-http4, it will try
to setup the proxy schema to be https4 when the real address is start from https. That is
not right. User should be able to define the scheme for the proxy himself. I just filled a
JIRA[1] for it.

You can workaround this issue by using the below option directly on the http4 endpoint uri.
"proxyAuthHost=12.42.454.56&proxyAuthPort=1132&proxyAuthScheme=http4"

[1]https://issues.apache.org/jira/browse/CAMEL-5595


-- 
Willem Jiang

FuseSource
Web: http://www.fusesource.com (http://www.fusesource.com/)
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English)
          http://jnn.javaeye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang 
Weibo: willemjiang





On Tuesday, September 11, 2012 at 6:15 PM, Adrian Harris wrote:

> Hi,
> 
> I have an issue when using the HTTP4 component to make a HTTPS call.
> 
> 1) I have the correct certificates in my keystore and truststore
> 2) I have the proxy server configured in my camel context properties
> 
> <properties>
> <property key="http.proxyHost" value="12.42.454.56" />
> <property key="http.proxyPort" value="1132" />
> </properties>
> 
> 3) My URI is of the form https4://app.company.com (http://app.company.com)
> 
> However the SSL appears to be lost, I assume when passing through the proxy
> server. The SSL debug trace of the handshake failure is below.
> 
> This was all working with the Camel HTTP component but I wanted to upgrade
> to the HTTP4 component.
> 
> Any help would be appreciated.
> 
> main, WRITE: SSLv2 client hello message, length = 101
> [Raw write]: length = 103
> 0000: 80 65 01 03 01 00 3C 00 00 00 20 00 00 04 01 00 .e....<... .....
> 0010: 80 00 00 05 00 00 2F 00 00 33 00 00 32 00 00 0A ....../..3..2...
> 0020: 07 00 C0 00 00 16 00 00 13 00 00 09 06 00 40 00 ..............@.
> 0030: 00 15 00 00 12 00 00 03 02 00 80 00 00 08 00 00 ................
> 0040: 14 00 00 11 00 00 FF 50 4F 06 DF 20 54 E6 A3 9F .......PO.. T...
> 0050: CA A0 3B F3 30 B0 E7 F1 C2 B5 D5 C9 34 13 1D 03 ..;.0.......4...
> 0060: BA E9 F6 A5 DB 00 38 ......8
> [Raw read]: length = 5
> 0000: 48 54 54 50 2F HTTP/
> main, handling exception: javax.net.ssl.SSLException: Unrecognized SSL
> message, plaintext connection?
> main, SEND TLSv1 ALERT: fatal, description = unexpected_message
> main, WRITE: TLSv1 Alert, length = 2
> [Raw write]: length = 7
> 0000: 15 03 01 00 02 02 0A .......
> main, called closeSocket()
> main, IOException in getSession(): javax.net.ssl.SSLException: Unrecognized
> SSL message, plaintext connection?
> main, called close()
> main, called closeInternal(true)
> main, called close()
> main, called closeInternal(true)
> 2012-09-11 10:39:43,170 [main ] ERROR DefaultErrorHandler 
> - Failed delivery for (MessageId: ID-CAR03-01597-52981-1347356374683-3-1 on
> ExchangeId: ID-CAR03-01597-52981-1347356374683-3-3). Exhausted after
> delivery attempt: 1 caught: javax.net.ssl.SSLPeerUnverifiedException: peer
> not authenticated
> 
> 
> 
> 
> --
> View this message in context: http://camel.465427.n5.nabble.com/Using-the-HTTP4-component-to-make-a-HTTPS-call-behinf-proxy-sever-tp5719105.html
> Sent from the Camel - Users mailing list archive at Nabble.com (http://Nabble.com).




Mime
View raw message