SQL Server

HTTP Request Boundary Property

Explains and demonstrates the HTTP request Boundary property. For multipart HTTP requests, Chilkat auto-generates a boundary string when the Boundary property is left unset (or empty). For example:

POST /something HTTP/1.1
Content-Type: multipart/form-data; boundary=------------090207000006060206010508
Host: domain
Content-Length: 378

--------------090207000006060206010508
Content-Disposition: form-data; name="fileA"; filename="fileA.txt"
Content-Type: text/plain

This is the contents of file A
--------------090207000006060206010508
Content-Disposition: form-data; name="fileB"; filename="fileB.txt"
Content-Type: text/plain

This is the contents of file B
--------------090207000006060206010508--

If the Boundary property is set, then Chilkat uses it. For example, if the Boundary property is set to "ABC123HELLOWORLD"

POST /something HTTP/1.1
Content-Type: multipart/form-data; boundary=ABC123HELLOWORLD
Host: domain
Content-Length: 318

--ABC123HELLOWORLD
Content-Disposition: form-data; name="fileA"; filename="fileA.txt"
Content-Type: text/plain

This is the contents of file A
--ABC123HELLOWORLD
Content-Disposition: form-data; name="fileB"; filename="fileB.txt"
Content-Type: text/plain

This is the contents of file B
--ABC123HELLOWORLD--

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

    EXEC sp_OASetProperty @req, 'HttpVerb', 'POST'
    EXEC sp_OASetProperty @req, 'Path', '/something'
    EXEC sp_OASetProperty @req, 'ContentType', 'multipart/form-data'

    DECLARE @success int
    EXEC sp_OAMethod @req, 'AddStringForUpload', @success OUT, 'fileA', 'fileA.txt', 'This is the contents of file A', 'utf-8'
    EXEC sp_OAMethod @req, 'AddStringForUpload', @success OUT, 'fileB', 'fileB.txt', 'This is the contents of file B', 'utf-8'

    -- When the Boundary property is empty (has not yet been set)
    -- Chilkat auto-generates a random boundary for the request.
    -- This should almost always be sufficient.
    -- For example, one can see the generated boundary here:
    EXEC sp_OAMethod @req, 'GenerateRequestText', @sTmp0 OUT
    PRINT @sTmp0

    -- If the Boundary property is set to a specific string, then the
    -- request will use it:
    EXEC sp_OASetProperty @req, 'Boundary', 'ABC123HELLOWORLD'
    EXEC sp_OAMethod @req, 'GenerateRequestText', @sTmp0 OUT
    PRINT @sTmp0

    EXEC @hr = sp_OADestroy @req


END
GO