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 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 _____ From: Pedro Quintas [mailto:[email protected]] Sent: Thursday, October 15, 2009 2:00 AM To: [email protected] 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 AuthSSLProtocolSocketFactory(endpoint), 443)); options.setTransportInProtocol(Constants.TRANSPORT_HTTPS); options.setProperty(HTTPConstants.AUTHENTICATE, authenticator); 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 WebService, 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!
