SQL Server

HTTP/HTTPS using SOCKS4 Proxy

See more HTTP Examples

Demonstrates how to use HTTP/HTTPS with a SOCKS4 proxy. SQL Server

-- 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 assumes the Chilkat HTTP API to have been previously unlocked.
    -- See Global Unlock Sample for sample code.

    DECLARE @http int
    EXEC @hr = sp_OACreate 'Chilkat.Http', @http OUT
    IF @hr <> 0
    BEGIN
        PRINT 'Failed to create ActiveX component'
        RETURN
    END

    -- Using a SOCKS4 proxy is just a matter of setting a few properties.
    -- Once these properties are set, all other coding is the same as when
    -- the connection is direct to the HTTP server.

    -- Set the SocksVersion property = 4 for SOCKS4
    EXEC sp_OASetProperty @http, 'SocksVersion', 4

    -- Set the SocksHostname to the SOCKS proxy domain name or IP address, 
    -- which may be IPv4 (dotted notation) or IPv6.
    EXEC sp_OASetProperty @http, 'SocksHostname', '192.168.1.100'

    -- The port where the SOCKS4 proxy is listening.
    EXEC sp_OASetProperty @http, 'SocksPort', 1080

    -- Now do whatever it is you need to do.  All communications will go through the proxy.
    DECLARE @html nvarchar(4000)
    EXEC sp_OAMethod @http, 'QuickGetStr', @html OUT, 'https://www.baidu.com/'
    EXEC sp_OAGetProperty @http, 'LastMethodSuccess', @iTmp0 OUT
    IF @iTmp0 <> 1
      BEGIN
        EXEC sp_OAGetProperty @http, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @http
        RETURN
      END


    PRINT @html

    PRINT '----'

    PRINT 'Success!'

    EXEC @hr = sp_OADestroy @http


END
GO