You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by lujan99 <lu...@gmail.com> on 2009/11/16 02:47:23 UTC

usign http componente with ssl

I build some test, and I have an error with all site https, example:
        <route>
          <from
uri="timer://foo?fixedRate=true&amp;delay=0&amp;period=30000"/>
          <to uri="https://www.google.com/accounts/ServiceLogin"/>
          <to uri="file://d:/work/camel"/>
        </route>

when I follow this request with ethereal I see:

192.168.1.99	190.17.124.232	SSLv2	Client Hello
190.17.124.232	192.168.1.99	TLSv1	Server Hello, Certificate, Server Hello
Done
192.168.1.99	190.17.124.232	TLSv1	Alert (Level: Fatal, Description:
Certificate Unknown)

I can get any result using https, 

how can I fix this issue??


-- 
View this message in context: http://old.nabble.com/usign-http-componente-with-ssl-tp26365801p26365801.html
Sent from the Camel - Users mailing list archive at Nabble.com.


Re: usign http componente with ssl

Posted by lujan99 <lu...@gmail.com>.
yes,I try with Firefox and IE and its ok.



willem.jiang wrote:
> 
> The test was added before the Camel 2.0 released, I don't think it's a 
> camel issue. Please check your network firewall, make sure you the 
> server 443 port is open for connection.
> 
> Willem
> lujan99 wrote:
>> My test is with ActiveMQ 5.3 / Camel 2.0
>> 
>> 
>> 
>> willem.jiang wrote:
>>> Hi
>>>
>>> First which version of Camel are you using?
>>> I just test the url within HttpsGetTest[1] on the trunk, everything 
>>> looks good.
>>>
>>> [1]https://svn.apache.org/repos/asf/camel/trunk/components/camel-http/src/test/java/org/apache/camel/component/http/HttpsGetTest.java
>>>
>>> Willem
>>>
>>> lujan99 wrote:
>>>> I build some test, and I have an error with all site https, example:
>>>>         <route>
>>>>           <from
>>>> uri="timer://foo?fixedRate=true&amp;delay=0&amp;period=30000"/>
>>>>           <to uri="https://www.google.com/accounts/ServiceLogin"/>
>>>>           <to uri="file://d:/work/camel"/>
>>>>         </route>
>>>>
>>>> when I follow this request with ethereal I see:
>>>>
>>>> 192.168.1.99	190.17.124.232	SSLv2	Client Hello
>>>> 190.17.124.232	192.168.1.99	TLSv1	Server Hello, Certificate, Server
>>>> Hello
>>>> Done
>>>> 192.168.1.99	190.17.124.232	TLSv1	Alert (Level: Fatal, Description:
>>>> Certificate Unknown)
>>>>
>>>> I can get any result using https, 
>>>>
>>>> how can I fix this issue??
>>>>
>>>>
>>>
>>>
>> 
> 
> 
> 

-- 
View this message in context: http://old.nabble.com/usign-http-componente-with-ssl-tp26365801p26394422.html
Sent from the Camel - Users mailing list archive at Nabble.com.


Re: usign http componente with ssl

Posted by lujan99 <lu...@gmail.com>.
I run ActiveMQ 5.3 with Camel 2.0 as windows service (windows 2003).
If I run activemq from console, https is ok and I got results.
the issue is when I run AMQ as windows service.




willem.jiang wrote:
> 
> The test was added before the Camel 2.0 released, I don't think it's a 
> camel issue. Please check your network firewall, make sure you the 
> server 443 port is open for connection.
> 
> Willem
> lujan99 wrote:
>> My test is with ActiveMQ 5.3 / Camel 2.0
>> 
>> 
>> 
>> willem.jiang wrote:
>>> Hi
>>>
>>> First which version of Camel are you using?
>>> I just test the url within HttpsGetTest[1] on the trunk, everything 
>>> looks good.
>>>
>>> [1]https://svn.apache.org/repos/asf/camel/trunk/components/camel-http/src/test/java/org/apache/camel/component/http/HttpsGetTest.java
>>>
>>> Willem
>>>
>>> lujan99 wrote:
>>>> I build some test, and I have an error with all site https, example:
>>>>         <route>
>>>>           <from
>>>> uri="timer://foo?fixedRate=true&amp;delay=0&amp;period=30000"/>
>>>>           <to uri="https://www.google.com/accounts/ServiceLogin"/>
>>>>           <to uri="file://d:/work/camel"/>
>>>>         </route>
>>>>
>>>> when I follow this request with ethereal I see:
>>>>
>>>> 192.168.1.99	190.17.124.232	SSLv2	Client Hello
>>>> 190.17.124.232	192.168.1.99	TLSv1	Server Hello, Certificate, Server
>>>> Hello
>>>> Done
>>>> 192.168.1.99	190.17.124.232	TLSv1	Alert (Level: Fatal, Description:
>>>> Certificate Unknown)
>>>>
>>>> I can get any result using https, 
>>>>
>>>> how can I fix this issue??
>>>>
>>>>
>>>
>>>
>> 
> 
> 
> 

-- 
View this message in context: http://old.nabble.com/usign-http-componente-with-ssl-tp26365801p26399299.html
Sent from the Camel - Users mailing list archive at Nabble.com.


Re: usign http componente with ssl

Posted by Willem Jiang <wi...@gmail.com>.
The test was added before the Camel 2.0 released, I don't think it's a 
camel issue. Please check your network firewall, make sure you the 
server 443 port is open for connection.

Willem
lujan99 wrote:
> My test is with ActiveMQ 5.3 / Camel 2.0
> 
> 
> 
> willem.jiang wrote:
>> Hi
>>
>> First which version of Camel are you using?
>> I just test the url within HttpsGetTest[1] on the trunk, everything 
>> looks good.
>>
>> [1]https://svn.apache.org/repos/asf/camel/trunk/components/camel-http/src/test/java/org/apache/camel/component/http/HttpsGetTest.java
>>
>> Willem
>>
>> lujan99 wrote:
>>> I build some test, and I have an error with all site https, example:
>>>         <route>
>>>           <from
>>> uri="timer://foo?fixedRate=true&amp;delay=0&amp;period=30000"/>
>>>           <to uri="https://www.google.com/accounts/ServiceLogin"/>
>>>           <to uri="file://d:/work/camel"/>
>>>         </route>
>>>
>>> when I follow this request with ethereal I see:
>>>
>>> 192.168.1.99	190.17.124.232	SSLv2	Client Hello
>>> 190.17.124.232	192.168.1.99	TLSv1	Server Hello, Certificate, Server Hello
>>> Done
>>> 192.168.1.99	190.17.124.232	TLSv1	Alert (Level: Fatal, Description:
>>> Certificate Unknown)
>>>
>>> I can get any result using https, 
>>>
>>> how can I fix this issue??
>>>
>>>
>>
>>
> 


Re: usign http componente with ssl

Posted by lujan99 <lu...@gmail.com>.
My test is with ActiveMQ 5.3 / Camel 2.0



willem.jiang wrote:
> 
> Hi
> 
> First which version of Camel are you using?
> I just test the url within HttpsGetTest[1] on the trunk, everything 
> looks good.
> 
> [1]https://svn.apache.org/repos/asf/camel/trunk/components/camel-http/src/test/java/org/apache/camel/component/http/HttpsGetTest.java
> 
> Willem
> 
> lujan99 wrote:
>> I build some test, and I have an error with all site https, example:
>>         <route>
>>           <from
>> uri="timer://foo?fixedRate=true&amp;delay=0&amp;period=30000"/>
>>           <to uri="https://www.google.com/accounts/ServiceLogin"/>
>>           <to uri="file://d:/work/camel"/>
>>         </route>
>> 
>> when I follow this request with ethereal I see:
>> 
>> 192.168.1.99	190.17.124.232	SSLv2	Client Hello
>> 190.17.124.232	192.168.1.99	TLSv1	Server Hello, Certificate, Server Hello
>> Done
>> 192.168.1.99	190.17.124.232	TLSv1	Alert (Level: Fatal, Description:
>> Certificate Unknown)
>> 
>> I can get any result using https, 
>> 
>> how can I fix this issue??
>> 
>> 
> 
> 
> 

-- 
View this message in context: http://old.nabble.com/usign-http-componente-with-ssl-tp26365801p26369458.html
Sent from the Camel - Users mailing list archive at Nabble.com.


Re: usign http componente with ssl

Posted by Willem Jiang <wi...@gmail.com>.
Hi

First which version of Camel are you using?
I just test the url within HttpsGetTest[1] on the trunk, everything 
looks good.

[1]https://svn.apache.org/repos/asf/camel/trunk/components/camel-http/src/test/java/org/apache/camel/component/http/HttpsGetTest.java

Willem

lujan99 wrote:
> I build some test, and I have an error with all site https, example:
>         <route>
>           <from
> uri="timer://foo?fixedRate=true&amp;delay=0&amp;period=30000"/>
>           <to uri="https://www.google.com/accounts/ServiceLogin"/>
>           <to uri="file://d:/work/camel"/>
>         </route>
> 
> when I follow this request with ethereal I see:
> 
> 192.168.1.99	190.17.124.232	SSLv2	Client Hello
> 190.17.124.232	192.168.1.99	TLSv1	Server Hello, Certificate, Server Hello
> Done
> 192.168.1.99	190.17.124.232	TLSv1	Alert (Level: Fatal, Description:
> Certificate Unknown)
> 
> I can get any result using https, 
> 
> how can I fix this issue??
> 
>