Originally posted by: repanzer
I'm building a map to do an HTTP POST to a Webservice which is under an HTTPS address. The description to follow is what I'm using to achieve this, and maybe I can use it, but if anyone has info in regarding hitting an HTTPS URL without the security option, possibly with a customer adapter, or any way, it will be greatly appreciated.
We do not have the security adapter and have no plans on purchasing it, but in the HTTP documentation, there is an adpater command "TUNNELING", of which the description is;
Tunneling (-TUNNELING)
Use the Tunneling adapter command (-TUNNELING) to establish a clean TCP connection to the proxy server and then upgrade to SSL using the CONNECT method. This command should only be used in cases where the specified proxy URL is non-secure (http) and the request URL is secure (https).
-TUNNELING For example, if you specify:
-url <https://secure-server:8080/example>
-proxy <http://user@proxy-server:2888> -tunneling
This command specifies
-
the entry to search for the HTTPS server called secure-server on port 8080 and request the example page
-
the proxy server called proxy-server with a plain (non-secure) HTTP connection
-
that the tunneling mechanism should be used to upgrade the non-secure proxy connection to a secure one for accessing the given URL
Unde the HTTP URL adapter command where it says HTTPS, it says; Note: This option is only available if you have the Security Option installed. That note is not under TUNNELING, so I'm assuming we don't need it to use tunneling. I'm still having problem and reaching out to our HTTP Proxy team to see if it's the ID I'm using and whether it has access to HTTPS, but when I do try now, my trace files shows;
Using http: protocol.
Using HTTP/1.1.
WSAStart: Entering WSAStart: bWSStarted = 0, nWSClients = 0 Sockets Client ID 1 enabled.
WSAStart: Exiting (rc = 1) WSAEnableSSL: SSL services not available.
WSATerm: Entering WSATerm: bWSStarted = 1, nWSClients = 1 Sockets Client ID 1 disabled.
WSATerm: nWSClients remaining = 0 WSATerm: Exiting SSL init failed.
Attempt #1 failed, no more retries allowed.
#IBM-Websphere-Transformation-Extender#IBMSterlingTransformationExtender#DataExchange