DataFlex

HTTPS multipart/form-data POST

See more HTTP Examples

Demonstrates how to send a multipart/form-data POST over HTTPS (using TLS). DataFlex

Use ChilkatAx-win32.pkg

Procedure Test
    Boolean iSuccess
    Variant vReq
    Handle hoReq
    String sPathToFileOnDisk
    String sFileContents
    Handle hoHttp
    Variant vResp
    Handle hoResp
    String sHtmlStr
    String sTemp1
    Integer iTemp1

    Move False To iSuccess

    // This example assumes the Chilkat HTTP API to have been previously unlocked.
    // See Global Unlock Sample for sample code.

    // This example demonstrates how to send a multipart/form-data POST that
    // looks like this:

    // 	POST /cgi/XXX.pl HTTP/1.0
    // 	Accept: text/html
    // 	Connection: Keep-Alive
    // 	User-Agent: XXX/8.0.15
    // 	Content-type: multipart/form-data, boundary=XXXxyxy
    // 	Content-Length: 682
    // 
    // 	--XXXxyxy
    // 	content-disposition: form-data; name="UploadAgent"
    // 
    // 	InterfaceVersion1.5
    // 	--XXXxyxy
    // 	content-disposition: form-data; name="user"
    // 
    // 	userValue
    // 	--XXXxyxy
    // 	content-disposition: form-data; name="password"
    // 
    // 	passwordValue
    // 	--XXXxyxy
    // 	content-disposition: form-data; name="file"
    // 
    // 	fileValue
    // 	--XXXxyxy
    // 	content-disposition: form-data; name="data_version"
    // 
    // 	dataVersion
    // 	--XXXxyxy
    // 	content-disposition: form-data; name="content2"; filename="XXX"
    // 
    // 	THE FILE CONTENT GOES HERE...
    // 	--XXXxyxy--
    // 

    // First, let's build the HTTP request object
    Get Create (RefClass(cComChilkatHttpRequest)) To hoReq
    If (Not(IsComObjectCreated(hoReq))) Begin
        Send CreateComObject of hoReq
    End

    Set ComHttpVerb Of hoReq To "POST"
    Set ComPath Of hoReq To "/cgi/XXX.pl"

    // The boundary string is automatically generated and added by Chilkat.
    // The value for the boundary string doesn't matter. (As long as it's a unique string that doesn't occur elsewhere in the request.)
    Set ComContentType Of hoReq To "multipart/form-data"

    // Adding the Connection: Keep-Alive is optional.  It only makes sense if the intent is to send
    // additional requests to the same domain (your-namespace-sb.accesscontrol.windows.net) within a reasonable time period.
    Send ComAddHeader To hoReq "Connection" "Keep-Alive"

    // --------------------------------------------------
    // IMPORTANT: Never set the Content-Length header.  
    // Chilkat will automatically compute the correct Content-Length and will add it.
    // --------------------------------------------------

    // If a specific User-Agent header field is needed, it can be added by calling AddHeader.
    Send ComAddHeader To hoReq "User-Agent" "XXX/8.0.15"

    // The "Accept" header, if present, tells the server what Content-Type responses will be accepted.
    // In this case, we're telling the server that we'll only accept "text/html" responses, and therefore
    // the server SHOULD only send a text/html response.  Technically, the Accept header is not required.
    Send ComAddHeader To hoReq "Accept" "text/html"

    // Add the params to the request.  Given that the Content-Type is set to "multipart/form-data", when
    // Chilkat composes the request, it will put each param in it's own MIME sub-part (i.e. in it's own
    // part delimited by the boundary string).
    Send ComAddParam To hoReq "UploadAgent" "InterfaceVersion1.5"
    Send ComAddParam To hoReq "user" "userValue"
    Send ComAddParam To hoReq "password" "passwordValue"
    Send ComAddParam To hoReq "file" "fileValue"
    Send ComAddParam To hoReq "data_version" "dataVersion"

    // The last param is the contents of a file.
    // If it's a file on disk, we can add it like this:
    Move "c:/someDir/someFile.dat" To sPathToFileOnDisk
    Get ComAddFileForUpload Of hoReq "content2" sPathToFileOnDisk To iSuccess
    If (iSuccess = False) Begin
        Get ComLastErrorText Of hoReq To sTemp1
        Showln sTemp1
        Procedure_Return
    End

    // Alternatively, if the contents of the file are in memory, perhaps in a string
    // variable, the file can be added like this instead.
    Move "This is the content of the file being uploaded." To sFileContents
    Get ComAddStringForUpload Of hoReq "content2" "XXX" sFileContents "utf-8" To iSuccess

    // -----------------------------------------------------------
    // IMPORTANT: To duplicate the HTTP request shown above, you'll want to choose 
    // either AddStringForUpload or AddFileForUpload, but not both.  It's possible to upload
    // any number of files by calling AddStringForUpload and/or AddFileForUpload any number
    // of times, once per file to be uploaded.  This of course assumes that the receiving
    // end is programmed to receive multiple files..
    // ------------------------------------------------------------

    Get Create (RefClass(cComChilkatHttp)) To hoHttp
    If (Not(IsComObjectCreated(hoHttp))) Begin
        Send CreateComObject of hoHttp
    End

    // The request is ready... now send it using HTTPS (which is port 443 by default).

    Get Create (RefClass(cComChilkatHttpResponse)) To hoResp
    If (Not(IsComObjectCreated(hoResp))) Begin
        Send CreateComObject of hoResp
    End
    Get pvComObject of hoReq to vReq
    Get pvComObject of hoResp to vResp
    Get ComHttpSReq Of hoHttp "www.myserver.com" 443 True vReq vResp To iSuccess
    If (iSuccess = False) Begin
        Get ComLastErrorText Of hoHttp To sTemp1
        Showln sTemp1
        Procedure_Return
    End

    Get ComStatusCode Of hoResp To iTemp1
    Showln "HTTP response status: " iTemp1

    // In this case, the response would be HTML because our Accept header
    // told the server to only return HTML.  The HTML is available on the BodyStr
    // property of the response object:
    Get ComBodyStr Of hoResp To sHtmlStr
    Showln "Received:"
    Showln sHtmlStr


End_Procedure