SQL Server

HTTPS Requests over Squid Proxy Direct TLS Connection

See more HTTP Examples

Demonstrates how to send HTTP requests through an HTTP proxy that supports Direct TLS Connections. (Chilkat tests with a squid 4.11 proxy.)

A direct TLS connection to an HTTP proxy is where the initial connection to the proxy server is TLS.

Note: This example requires Chilkat v9.5.0.83 or greater.

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 requires the Chilkat 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

    -- Set the HTTP proxy domain or IP address.
    EXEC sp_OASetProperty @http, 'ProxyDomain', '172.16.16.46'
    -- The proxy port..
    EXEC sp_OASetProperty @http, 'ProxyPort', 3128

    -- Indicate that we are to use a direct TLS connection with the HTTP proxy
    -- (we use a Squid Cache: Version 4.11 for testing)
    EXEC sp_OASetProperty @http, 'ProxyDirectTls', 1

    -- If the proxy requires a login or password, we can set it here.
    -- Otherwise comment out these lines.
    EXEC sp_OASetProperty @http, 'ProxyLogin', 'myProxyLogin'
    EXEC sp_OASetProperty @http, 'ProxyPassword', 'myProxyPassword'

    -- All requests sent on the http object will now go through the proxy.
    -- Give it a test:
    DECLARE @s nvarchar(4000)
    EXEC sp_OAMethod @http, 'QuickGetStr', @s OUT, 'https://www.chilkatsoft.com/helloWorld.html'
    EXEC sp_OAGetProperty @http, 'LastMethodSuccess', @iTmp0 OUT
    IF @iTmp0 = 0
      BEGIN
        EXEC sp_OAGetProperty @http, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @http
        RETURN
      END

    -- The LastErrorText property also contains information when method call succeeds.
    -- Have a look to see that the request was sent through the proxy:
    EXEC sp_OAGetProperty @http, 'LastErrorText', @sTmp0 OUT
    PRINT @sTmp0


    PRINT '---'

    PRINT @s

    PRINT '---'

    PRINT 'Success for TLS destination over direct TLS HTTP proxy.'

    EXEC @hr = sp_OADestroy @http


END
GO