SQL Server

Using an HTTP Proxy for HTTP POST's, GET's, etc.

See more HTTP Examples

Demonstrates how to use an HTTP proxy for HTTP requests. 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
    -- This example assumes 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

    -- To use an HTTP proxy, set the following properties

    -- Use a domain name or IP address.
    EXEC sp_OASetProperty @http, 'ProxyDomain', '172.16.16.24'

    -- The port at which your HTTP proxy is listening for HTTP requests.
    EXEC sp_OASetProperty @http, 'ProxyPort', 808

    -- If your HTTP proxy requires authentication...
    EXEC sp_OASetProperty @http, 'ProxyLogin', 'myProxyLogin'
    EXEC sp_OASetProperty @http, 'ProxyPassword', 'myProxyPassword'

    -- At this point, all Chilkat HTTP methods for sending POST's, GET's, or anything else
    -- will use the HTTP proxy.  The remainder of your code is the same.
    -- Using an HTTP proxy only requires the above properties to be set beforehand...

    EXEC @hr = sp_OADestroy @http


END
GO