Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 23650 invoked from network); 15 Oct 2009 08:06:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 Oct 2009 08:06:34 -0000 Received: (qmail 77521 invoked by uid 500); 15 Oct 2009 08:06:32 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 77439 invoked by uid 500); 15 Oct 2009 08:06:32 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 77430 invoked by uid 99); 15 Oct 2009 08:06:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Oct 2009 08:06:32 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [213.58.173.117] (HELO EXCH-ET.first.pt) (213.58.173.117) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Oct 2009 08:06:22 +0000 Received: from EXCH-HTCA.first.pt (192.168.40.253) by EXCH-ET.first.pt (192.168.10.1) with Microsoft SMTP Server (TLS) id 8.1.393.1; Thu, 15 Oct 2009 09:05:59 +0100 Received: from EXCH-MBOX.first.pt ([::1]) by exch-htca.first.pt ([192.168.20.18]) with mapi; Thu, 15 Oct 2009 09:05:58 +0100 From: Pedro Quintas To: "axis-user@ws.apache.org" Importance: high X-Priority: 1 Date: Thu, 15 Oct 2009 09:05:56 +0100 Subject: RE: HTTPS WebService through HTTP Proxy Thread-Topic: HTTPS WebService through HTTP Proxy Thread-Index: AcpNaAnXHdgIvtwBTGyKvP8CpWQC5AABLuhw Message-ID: References: In-Reply-To: Accept-Language: pt-PT Content-Language: pt-PT X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: pt-PT Content-Type: multipart/alternative; boundary="_000_A37DC403650D714F8FD75830E6E9547E767767568AEXCHMBOXfirst_" MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_A37DC403650D714F8FD75830E6E9547E767767568AEXCHMBOXfirst_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I don't agreed with you. The Client must know that on the other side (WebService) talks in HTTPS. For example, I use SOAPUI to test this connections and again I put the TCPM= on between the SOAPUI and the proxy. I saw in plaintext the communication with the proxy: CONNECT portal.pt:443 HTTP/1.1 Proxy-Authorization: Basic dGVzdGU6dGVzdGU=3D User-Agent: Jakarta Commons-HttpClient/3.1 Host: portal.pt Proxy-Connection: Keep-Alive And Received from proxy this: HTTP/1.0 200 Connection established At this time, I'm connect to the portal.pt:443 server. >From here the difference starts, on my client all the communication continu= es in plaintext, on SOAPUI all the communication is encrypted. Is I use my client without the proxy setting all works fine (the communicat= ion is encrypted). Any ideas? Thanks, Kintas De: Christian Gosch [mailto:christian.gosch@inovex.de] Enviada: quinta-feira, 15 de Outubro de 2009 08:18 Para: axis-user Assunto: RE: HTTPS WebService through HTTP Proxy I'm not quite sure, but shouldn't it be sufficient to talk to the proxy as = required, and let the proxy do whatever it is supposed to? In other words: I think from an Axis client's view only the instance this c= lient directly talks to should matter. What happens there (immediate proces= sing or forwarding forth and back of the SOAP messages by means of a proxy = or gateway) should not matter at all for the Axis client. This applies to all aspects of the communication, i. e. ports, resource URL= s, encryption, authentication, authorization... Christian ________________________________ From: Pedro Quintas [mailto:pedro.quintas@first.pt] Sent: Thursday, October 15, 2009 2:00 AM To: axis-user@ws.apache.org Subject: HTTPS WebService through HTTP Proxy Importance: High Hello. I need to call a HTTPS WebService through a HTTP proxy. I set on Options object the following: options.setProperty(HTTPConstants.CUSTOM_PROTOCOL_HANDLER, = new Protocol("https", (ProtocolSocketFactory)new AuthSSLProtocolSocketFacto= ry(endpoint), 443)); options.setTransportInProtocol(Constants.TRANSPORT_HTTPS); options.setProperty(HTTPConstants.AUTHENTICATE, authenticat= or); options.setProperty(HTTPConstants.PROXY, proxyProperty); //= proxyProperty have set ProxyName, ProxyPort, UserName, PassWord And another options. I put the TCPMon, between my program and the proxy to see what is send. On TCPMon I see the connection made to the proxy and then to the HTTPS WebS= ervice, all in plaintext and this is wrong because after the connection to = the proxy, all data transmited should been encrypted. Any one already have this problem? How can I solve this? Sorry for my bad English. Thanks, Kintas !DSPAM:4ad66624326667108612316! --_000_A37DC403650D714F8FD75830E6E9547E767767568AEXCHMBOXfirst_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I don’t agreed with you.

The Client must know that on the other side (WebService) talks in HTTPS.

 

For example, I use SOAPUI to test this connections and again I put the TCPMon between the SOAPUI and the proxy.

I saw in plaintext the communication with the proxy:

 

CONNECT portal.pt:443 HTTP/1.1

Proxy-Authorization: Basic dGVzdGU= 6dGVzdGU=3D

User-Agent: Jakarta Commons-HttpClient/3.1

Host: portal.pt<= /p>

Proxy-Connection: Keep-Alive<= /o:p>

 

And Received from proxy this:

 

           &nb= sp;    HTTP/1.0 200 Connection established

 

At this time, I’m connect to the portal.pt:443 server.=

From here the difference starts, on my client all the communication continues in plaintext, on SOAPUI all the communication is encrypted.<= /p>

 

Is I use my client without the proxy setting all works fine (the communication i= s encrypted).

 

Any ideas?

 

 

Thanks,

Kintas

 

 

D= e: Christian Gosch [mailto:christian.gosch@inovex.de]
Enviada: quinta-feira, 15 de Outubro de 2009 08:18
Para: axis-user
Assunto: RE: HTTPS WebService through HTTP Proxy

 

I’m not quite sure, but shouldn’t it be sufficient = to talk to the proxy as required, and let the proxy do whatever it is supposed= to?

 

In other words: I think from an Axis client’s view only t= he instance this client directly talks to should matter. What happens there (immediate processing or forwarding forth and back of the SOAP messages by means of a proxy or gateway) should not matter at all for the Axis client. =

 

This applies to all aspects of the communication, i. e. ports, resource URLs, encryption, authentication, authorization...

 

Christian =

 


 &nbs= p;

From: Pedro Quintas [mailto:pedro.quintas@first.pt]
Sent: Thursday, October 15, 2009 2:00 AM
To: axis-user@ws.apache.org
Subject: HTTPS WebService through HTTP Proxy
Importance: High
<= /span>=

 =

Hello.

 

I need t= o call a HTTPS WebService  through a HTTP proxy.

I set on= Options object the following: =

&nb= sp;

 &n= bsp;            = ;  options.setProperty(HTTPConstants.CUSTOM_PROTOCOL_HANDLER, new Protocol(“https”, (ProtocolSocketFactory)new AuthSSLProtocolSocketFactory(endpoint), 443));

 &n= bsp;            = ;  options.setTransportInProtocol(Constants.TRANSPORT_HTTPS);

&nb= sp;

 &n= bsp;            = ;  options.setProperty(HTTPConstants.AUTHENTICATE, authenticator);

&nb= sp;

 &n= bsp;            = ;  options.setProperty(HTTPConstants.PROXY, proxyProperty); // proxyProperty h= ave set ProxyName, ProxyPort, UserName, PassWord

&nb= sp;

And anot= her options.

I put th= e TCPMon, between my program and the proxy to see what is send.

&nb= sp;

On TCPMo= n I see the connection made to the proxy and then to the HTTPS WebService, all in plaintext and this is wrong because after the connection to the proxy, all = data transmited should been encrypted.

&nb= sp;

Any one = already have this problem? How can I solve this?

&nb= sp;

Sorry fo= r my bad English.

&nb= sp;

&nb= sp;

Thanks,<= /span>

Kintas

!DSPAM:4ad66624326667108612316!

 

--_000_A37DC403650D714F8FD75830E6E9547E767767568AEXCHMBOXfirst_--