(SQL Server) Socket/SSL/TLS through SOCKS5 / SOCKS4 Proxy

Demonstrates how to use the Chilkat Socket/SSL/TLS component/library with a SOCKS5 or SOCKS4 proxy server.

Chilkat ActiveX Downloads ActiveX for 32-bit and 64-bit Windows

-- Important: See this note about string length limitations for strings returned by sp_OAMethod calls.
--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
    DECLARE @hr int
    DECLARE @iTmp0 int
    -- Important: Do not use nvarchar(max).  See the warning about using nvarchar(max).
    DECLARE @sTmp0 nvarchar(4000)
    -- This example requires the Chilkat API to have been previously unlocked.
    -- See Global Unlock Sample for sample code.

    DECLARE @socket int
    -- Use "Chilkat_9_5_0.Socket" for versions of Chilkat < 10.0.0
    EXEC @hr = sp_OACreate 'Chilkat.Socket', @socket OUT
    IF @hr <> 0
    BEGIN
        PRINT 'Failed to create ActiveX component'
        RETURN
    END

    -- To use a SOCKS4 or SOCKS5 proxy, simply set the following
    -- properties prior to calling Connect.  The connection may be SSL/TLS or 
    -- non-secure - both will work with a SOCKS proxy.
    -- The SOCKS hostname may be a domain name or 
    -- IP address:
    EXEC sp_OASetProperty @socket, 'SocksHostname', 'www.mysocksproxyserver.com'
    EXEC sp_OASetProperty @socket, 'SocksPort', 1080
    EXEC sp_OASetProperty @socket, 'SocksUsername', 'myProxyLogin'
    EXEC sp_OASetProperty @socket, 'SocksPassword', 'myProxyPassword'
    -- Set the SOCKS version to 4 or 5 based on the version
    -- of the SOCKS proxy server:
    EXEC sp_OASetProperty @socket, 'SocksVersion', 5
    -- Note: SOCKS4 servers only support usernames without passwords.
    -- SOCKS5 servers support full login/password authentication.

    -- Connect to port 5555 of 192.168.1.108.
    -- hostname may be a domain name or IP address.
    DECLARE @hostname nvarchar(4000)
    SELECT @hostname = '192.168.1.108'
    DECLARE @ssl int
    SELECT @ssl = 0
    DECLARE @maxWaitMillisec int
    SELECT @maxWaitMillisec = 20000
    DECLARE @success int
    EXEC sp_OAMethod @socket, 'Connect', @success OUT, @hostname, 5555, @ssl, @maxWaitMillisec
    IF @success <> 1
      BEGIN
        EXEC sp_OAGetProperty @socket, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @socket
        RETURN
      END

    -- Set maximum timeouts for reading an writing (in millisec)
    EXEC sp_OASetProperty @socket, 'MaxReadIdleMs', 10000
    EXEC sp_OASetProperty @socket, 'MaxSendIdleMs', 10000

    -- The server (in this example) is going to send a "Hello World!" 
    -- message.  Read it:
    DECLARE @receivedMsg nvarchar(4000)
    EXEC sp_OAMethod @socket, 'ReceiveString', @receivedMsg OUT
    EXEC sp_OAGetProperty @socket, 'LastMethodSuccess', @iTmp0 OUT
    IF @iTmp0 <> 1
      BEGIN
        EXEC sp_OAGetProperty @socket, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @socket
        RETURN
      END

    -- Close the connection with the server
    -- Wait a max of 20 seconds (20000 millsec)
    EXEC sp_OAMethod @socket, 'Close', @success OUT, 20000


    PRINT @receivedMsg

    EXEC @hr = sp_OADestroy @socket


END
GO