SQL Server

HTTP Verb - How to use any Verb (GET, PUT, POST, DELETE, PROPFIND, etc.)

The HttpVerb property may be set to anything. Typically, it is set to the common/standard HTTP verbs such as GET, POST, PUT, DELETE, etc. It can be set to anything, including custom verbs that only have meaning to your particular server-side application.

This example demonstrates how to compose an HTTP request using the PROPFIND verb, which is something one might use with a WebDAV request.

This example composes the following HTTP request:

   PROPFIND  /container/ HTTP/1.1
   Host: www.foo.bar
   Depth: 1
   Content-Type: text/xml; charset="utf-8"
   Content-Length: xxxx

   <?xml version="1.0" encoding="utf-8" ?>
   <D:propfind xmlns:D="DAV:">
     <D:allprop/>
   </D:propfind>

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
    -- Important: Do not use nvarchar(max).  See the warning about using nvarchar(max).
    DECLARE @sTmp0 nvarchar(4000)
    DECLARE @req int
    EXEC @hr = sp_OACreate 'Chilkat.HttpRequest', @req OUT
    IF @hr <> 0
    BEGIN
        PRINT 'Failed to create ActiveX component'
        RETURN
    END

    -- The ContentType, HttpVerb, and Path properties should
    -- always be explicitly set.
    EXEC sp_OASetProperty @req, 'HttpVerb', 'PROPFIND'
    EXEC sp_OASetProperty @req, 'Path', '/container/'
    EXEC sp_OASetProperty @req, 'ContentType', 'text/xml'
    EXEC sp_OASetProperty @req, 'Charset', 'utf-8'
    EXEC sp_OASetProperty @req, 'SendCharset', 1

    EXEC sp_OAMethod @req, 'AddHeader', NULL, 'Depth', '1'

    DECLARE @xml int
    EXEC @hr = sp_OACreate 'Chilkat.Xml', @xml OUT

    EXEC sp_OASetProperty @xml, 'Tag', 'propfind'
    DECLARE @success int
    EXEC sp_OAMethod @xml, 'AddAttribute', @success OUT, 'xmlns:D', 'DAV:'
    EXEC sp_OAMethod @xml, 'NewChild2', NULL, 'allprop', ''

    EXEC sp_OAMethod @xml, 'GetXml', @sTmp0 OUT
    EXEC sp_OAMethod @req, 'LoadBodyFromString', @success OUT, @sTmp0, 'utf-8'

    -- View the request that would be sent if HttpSReq was called:
    DECLARE @requestMime nvarchar(4000)
    EXEC sp_OAMethod @req, 'GenerateRequestText', @requestMime OUT

    PRINT @requestMime

    -- A few important comments about the HTTP request that is generated:
    -- 
    -- 1) The Content-Length header is automatically generated based on the actual length of the MIME message
    --    that follows the intial (topmost) MIME header.
    -- 2) The HOST header will automatically get filled in with the actual domain when HttpSReq
    --    is called

    EXEC @hr = sp_OADestroy @req
    EXEC @hr = sp_OADestroy @xml


END
GO