SQL Server

HTTP multipart/form-data Upload

See more HTTP Examples

Demonstrates how to upload files to an HTTP server using a multipart/form-data POST. 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)
    DECLARE @success int
    SELECT @success = 0

    -- 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

    DECLARE @req int
    EXEC @hr = sp_OACreate 'Chilkat.HttpRequest', @req OUT

    EXEC sp_OASetProperty @req, 'HttpVerb', 'POST'
    EXEC sp_OASetProperty @req, 'ContentType', 'multipart/form-data'
    EXEC sp_OASetProperty @req, 'Path', 'rcvFormDataUpload.aspx'

    -- Send an "Expect: 100-continue" header in the request.
    -- This causes the HTTP server to end a 100-continue response
    -- immediately after receiving the HTTP header.  The client
    -- (Chilkat) will receive this intermediate response, and if
    -- it's not an error response, it knows that the HTTP server will
    -- accept the data that is forthcoming.
    -- The alternative is to get an error response after trying to upload
    -- the entire contents of the files.
    EXEC sp_OAMethod @req, 'AddHeader', NULL, 'Expect', '100-continue'

    -- Call AddFileForUpload2 for each file to be uploaded in the HTTP multipart/form-data POST
    -- To allow Chilkat to determine the content-type automatically based on file-extension,
    -- call AddFileForUpload instead.

    -- The 1st arg is the filename passed in the HTTP request.
    -- The 2nd arg is the path in the local filesytem.
    -- The file is not loaded into memory.  It is streamed directly from the file
    -- when the HTTP POST is sent.
    EXEC sp_OAMethod @req, 'AddFileForUpload2', @success OUT, 'starfish.jpg', 'c:/qa_data/starfish.jpg', 'image/jpg'
    IF @success = 0
      BEGIN
        EXEC sp_OAGetProperty @req, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @http
        EXEC @hr = sp_OADestroy @req
        RETURN
      END

    EXEC sp_OAMethod @req, 'AddFileForUpload', @success OUT, 'something.pdf', 'c:/qa_data/something.pdf'
    IF @success = 0
      BEGIN
        EXEC sp_OAGetProperty @req, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @http
        EXEC @hr = sp_OADestroy @req
        RETURN
      END

    -- Its also possible to add a file from a string:
    EXEC sp_OAMethod @req, 'AddStringForUpload', @success OUT, 'test.xml', 'test.xml', '<abc>This is the test.xml content</abc>', 'utf-8'
    -- We'll assume success since no files are involved..

    -- This sends the HTTP request (with 3 files being uploaded) to
    -- http://www.mywebserver123abc.com/rcvFormDataUpload.aspx
    DECLARE @resp int
    EXEC @hr = sp_OACreate 'Chilkat.HttpResponse', @resp OUT

    EXEC sp_OAMethod @http, 'HttpSReq', @success OUT, 'www.mywebserver123abc.com', 80, 0, @req, @resp
    IF @success = 0
      BEGIN
        EXEC sp_OAGetProperty @http, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @http
        EXEC @hr = sp_OADestroy @req
        EXEC @hr = sp_OADestroy @resp
        RETURN
      END


    EXEC sp_OAGetProperty @resp, 'StatusCode', @iTmp0 OUT
    PRINT 'HTTP response status: ' + @iTmp0
    -- See the online reference documentation for 
    -- other information that can be obtained from the response object.

    -- To send using SSL/TLS, do this instead.
    -- This sends to https://www.mywebserver123abc.com/rcvFormDataUpload.aspx
    EXEC sp_OAMethod @http, 'HttpSReq', @success OUT, 'www.mywebserver123abc.com', 443, 1, @req, @resp
    IF @success = 0
      BEGIN
        EXEC sp_OAGetProperty @http, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @http
        EXEC @hr = sp_OADestroy @req
        EXEC @hr = sp_OADestroy @resp
        RETURN
      END


    EXEC sp_OAGetProperty @resp, 'StatusCode', @iTmp0 OUT
    PRINT 'HTTP response status: ' + @iTmp0
    -- See the online reference documentation for 
    -- other information that can be obtained from the response object.

    EXEC @hr = sp_OADestroy @http
    EXEC @hr = sp_OADestroy @req
    EXEC @hr = sp_OADestroy @resp


END
GO